Crypto payments

Relentless Identity accepts crypto payments as a second payment rail beside Stripe.

Two supported paths

• Signed-in dashboard checkout: create a hosted invoice, scan a QR code, and fund a stored crypto balance for your workspace.
• Accountless prepaid access: buy a wallet-funded credit bundle from $1 upward and receive a bearer token immediately after settlement.

Signed-in dashboard checkout

• Available from the billing workspace through a hosted invoice modal with QR-code payment instructions.
• This is the human-friendly crypto path for authenticated users.
• Every successful invoice credits your workspace's stored crypto balance.
• When you select a self-serve subscription or PAYG target in billing, the app debits that stored balance.
• Charges are 10% lower than the Stripe catalog because the settlement rail is crypto-native.
• Subscription terms paid this way renew only when the account has enough stored crypto balance. If not, the term ends at the current billing-period boundary.
• PAYG purchased during an active subscription cycle expires at the next paid renewal. Standalone PAYG balance otherwise remains until consumed.

Accountless prepaid access

The public x402 purchase endpoint is:

POST https://app.relentlessidentity.com/api/x402/purchase?kind=flex&amountCents=100

Rules:

• kind=flex is the accountless prepaid path.
• amountCents must be at least 100.
• The usage value scales from the nearest configured pay-as-you-go tier at or below the amount being purchased. That means $1-$28.99 can follow the $14 tier economics, $29-$48.99 can follow the $29 tier economics, and so on.
• Accountless x402 purchases use the same pay-as-you-go catalog pricing as signed-in PAYG purchases.
• The response returns a bearer token after settlement. Save it and reuse it until the prepaid balance is exhausted.
• The response also includes a pricing block with the purchased amount, the charged amount, and the computed usage value in micros.

Endpoint expectations

• POST /client/attempt: for one Finder lookup.
• POST /client/probe: for one mailbox check.
• POST /client/probe/batch: for a smaller list of mailboxes. Use the job endpoint for larger lists.
• POST /client/jobs/finder and POST /client/jobs/probe-batch: use these when you want asynchronous completion and callback support.

Catalog pricing examples

Example accountless purchases

Current pay-as-you-go tiers

Renewal behavior for crypto subscriptions

• The initial signed-in crypto subscription purchase debits your stored crypto balance and activates the current term immediately.
• Additional balance top-ups made while the account is on a crypto subscription are stored as prepaid renewal balance.
• When the current term ends, the app automatically attempts to debit the next discounted crypto renewal amount from that stored balance.
• If enough balance exists, the next term starts and the usage pool resets.
• If not, the subscription moves to an expired state and access stops at the period boundary.

Typical response shape after a successful accountless purchase:

{
  "ok": true,
  "provider": "x402",
  "sessionId": "<payment-session-id>",
  "pricing": {
    "nominalAmountCents": 100,
    "chargedAmountCents": 100,
    "grantedValueMicros": 1000000
  },
  "token": "relid_pat_...",
  "docsUrl": "/docs/crypto-payments"
}

Authentication after payment

The returned bearer token uses the same request format as dashboard-issued access tokens:

Authorization: Bearer relid_pat_...

That token can call:

• POST /client/attempt
• POST /client/probe
• POST /client/probe/batch
• GET /client/usage
• GET /client/history
• MCP tool calls that use bearer authentication

Recovery

If you already completed payment and only need the issued bearer token again, redeem the recorded payment session:

GET https://app.relentlessidentity.com/api/x402/purchase/redeem?sessionId=<payment-session-id>

Notes

• Signed-in crypto invoice checkout requires a signed-in workspace account.
• Accountless wallet purchases are intended for direct REST and MCP access.
• The current accountless x402 route provisions prepaid credits, not auto-renewing subscriptions.
• The settlement transaction hash is stored as immutable billing audit data.