Method.tempo.subscription

Choose a signing account

import { privateKeyToAccount } from 'viem/accounts'

export const account = privateKeyToAccount(process.env.PRIVATE_KEY as `0x${string}`)

Creates a Tempo subscription client method for signing access-key authorizations.

Usage

With request validation

Use validateRequest to enforce local client policy before signing.

With explicit access key

Most servers include an access key in the Challenge. Pass accessKey only when the server expects the client to supply a specific key.

Return type

import type { Method } from 'mppx'
 
type ReturnType = Method.Client

Parameters

accessKey (optional)

• Type: SubscriptionAccessKey

Access key authorized by the root account. Omit this when the Challenge includes methodDetails.accessKey.

account (optional)

• Type: Account | Address

Account that signs the key authorization. You can override this per request with fetch context.

getClient (optional)

• Type: (parameters: { chainId?: number }) => MaybePromise<Client>

Function that returns a viem client for the given Tempo chain ID.

validateRequest (optional)

• Type: (request: SubscriptionRequest) => MaybePromise<void>

Runs before the client signs the key authorization. Throw to reject subscription terms.

Context

Pass request-specific values through fetch context when needed.

accessKey (optional)

• Type: SubscriptionAccessKey

Access key to use for this request.

account (optional)

• Type: Account | Address

Account to use for this request.

Cancellation

tempo.subscription() doesn't expose a client-side cancel method. Call the service's cancellation endpoint so the server can mark the subscription canceledAt. You can also revoke the Tempo access key from the payer account as a wallet-level backstop.

await fetch('https://api.example.com/subscription/cancel', {
  method: 'POST',
})

import { createClient, http } from 'viem'
import { tempo } from 'viem/chains'
import { privateKeyToAccount } from 'viem/accounts'
import { Actions } from 'viem/tempo'
 
const client = createClient({
  account: privateKeyToAccount(
    '0x0000000000000000000000000000000000000000000000000000000000000001', // your account
  ),
  chain: tempo,
  transport: http(),
})
 
await Actions.accessKey.revokeSync(client, {
  accessKey: '0x70997970C51812dc3A010C7d01b50e0d17dc79C8',
})

Revocation blocks future access-key charges, but it doesn't update the merchant's subscription record. Treat it as a backstop, not the primary cancellation flow.