Crypto checkout

Driftstack supports cryptocurrency payments through NowPayments. The flow mints a one-time payment address per order; the customer sends crypto; NowPayments posts an IPN to Driftstack when the payment is confirmed on-chain; Driftstack activates the subscription tier.

A crypto payment is a one-time payment covering one month: it entitles the purchased tier for a fixed 31-day term and then lapses unless a new order is paid (there is no auto-charge and no stored payment method). Re-buying the same tier stacks onto the running term; when a term ends the account is recomputed to its best remaining coverage (a live card subscription, another still-valid crypto entitlement, or the free tier). See the Paying with crypto guide for the customer-facing walkthrough.

Crypto checkout is enabled for paid tiers ($79/mo and above). NowPayments enforces an empirical USD-equivalent floor (~$19.16) below which payments are rejected as amount_too_low, and Driftstack short-circuits any order under $20 (NOWPAYMENTS_MIN_USD_CENTS = 2000) before it reaches NowPayments. Every current tier ($79+) clears both thresholds.

Create a checkout order

POST /v1/billing/crypto-checkout

const order = await client.cryptoOrders.createCheckout({
  product: 'solo_manual',
  // price_cents + price_currency are accepted for API compatibility
  // but IGNORED by the server. The price is derived server-side
  // from the product slug to prevent price tampering.
  price_cents: 7900,
  price_currency: 'USD',
});

Requires the admin:billing scope — starting a crypto checkout is a billing operation. (The same applies to the other mutating crypto endpoints: PATCH /v1/billing/crypto-orders/:id and POST /v1/billing/crypto-orders/:id/cancel. Read endpoints — listing orders, fetching a single order, and all three receipt variants — require read:billing. Note that granular admin:billing does NOT satisfy read:billing: only the broad read scope or account_owner does. A key scoped ['admin:billing'] alone can therefore create an order and then 403 on every status poll, so mint checkout keys with both, or with account_owner.) Idempotent — pass an Idempotency-Key header to make retries safe; a repeated key returns the original order verbatim (with an Idempotent-Replayed: 1 response header) for as long as the order row exists — there is no 24-hour expiry. See Idempotency keys for which endpoints honour the header and which ignore it.

Returns:

{
  "order_id": "ord_a1b2c3d4e5f6",
  "product": "solo_manual",
  "price_cents": 7900,
  "price_currency": "USD",
  "status": "pending",
  "provider": "nowpayments",
  "payment_address": "bc1qexample...",
  "pay_currency": "btc",
  "pay_amount": 0.00123,
  "created_at": "2026-05-22T10:00:00Z"
}

Send exactly pay_amount pay_currency to payment_address. The customer-dashboard UI renders this address in a copy-friendly modal; SDK consumers should mirror that pattern. Underpayment puts the order in the partial state (not credited as paid); overpayment is treated as fully paid and the surplus stays on the NowPayments side (issue a refund manually via the NowPayments dashboard if needed).

Supported products

For a product priced below the NowPayments USD floor, the API returns an unavailable checkout response (provider: "stub" with null payment fields) and makes no upstream call. Every current tier clears the floor; the guard prevents a future mispriced product from creating an invalid checkout.

Order status lifecycle

pending → confirming → paid
       ↘  partial    → paid (top-up) | failed
       ↘  cancelled (customer-initiated)
       ↘  failed (timeout / refund / expired)

Terminal states (paid, failed, cancelled) cannot transition out. A late-arriving payment to a cancelled order leaves the order cancelled but records the payment_id for support reconciliation.

Price a product before ordering

POST /v1/billing/crypto-checkout/quote

Returns the price a checkout order would be created for, without creating one. Requires the read:billing scope. The quote reads the same pricing source as order creation, so the preview always equals the amount you will be charged.

{ "product": "solo_manual" }

{ "product": "solo_manual", "price_cents": 7900, "price_currency": "USD" }

Receipts

GET /v1/billing/crypto-orders/:order_id/receipt

Every order has a receipt in three formats, all requiring read:billing:

Like every endpoint on this page they are scoped to the calling account: an order id belonging to someone else returns 404, not 403, so the API never confirms that another account’s order exists.

List customer orders

GET /v1/billing/crypto-orders

Returns the authenticated customer’s crypto orders, newest first.

{
  "orders": [
    {
      "order_id": "ord_a1b2c3d4e5f6",
      "product": "solo_manual",
      "price_cents": 7900,
      "price_currency": "USD",
      "payment_id": "12345678",
      "status": "paid",
      "customer_note": null,
      "events": [
        { "status": "pending", "at": "2026-05-20T12:00:00.000Z", "source": "create" },
        { "status": "confirming", "at": "2026-05-20T12:01:00.000Z", "source": "ipn" },
        { "status": "paid", "at": "2026-05-20T12:10:00.000Z", "source": "ipn" }
      ],
      "expires_at": null,
      "created_at": "2026-05-20T12:00:00.000Z",
      "updated_at": "2026-05-20T12:10:00.000Z"
    }
  ],
  "next_cursor": null
}

Timestamps are ISO-8601 strings. The list is cursor-paginated: pass the returned next_cursor back as ?cursor=<...> to fetch the next page (null means no more pages). expires_at is set only while an order is pending; it is null once the order resolves.

events is an append-only state-transition log — the canonical record of how the order reached its current state, for support forensics.

Webhook event: crypto.order.paid

When an order transitions to paid, Driftstack fires a crypto.order.paid webhook event to your configured endpoints.

{
  "id": "<uuid>",
  "type": "crypto.order.paid",
  "created_at": "2026-05-22T10:30:00.000Z",
  "data": {
    "order_id": "ord_a1b2c3d4e5f6",
    "product": "solo_manual",
    "price_cents": 7900,
    "price_currency": "USD",
    "payment_id": "12345678",
    "paid_at": "2026-05-22T10:30:00Z"
  }
}

Same canonical envelope (id / type / created_at / data) and HMAC-SHA256 signature scheme as every other Driftstack webhook (webhook signing). Idempotent: delivery is retried up to 5 times after the initial attempt (6 attempts total) if your endpoint returns non-2xx, each carrying the same top-level id — dedup on that id (also surfaced as X-Driftstack-Event-Id).

The companion crypto.order.failed event fires on the pending|confirming|partial → failed transition (driven by an IPN status or an admin sweep — a customer cancellation moves the order to cancelled and fires no event).

Idempotency

Same contract as the rest of the API. Send an Idempotency-Key header (1-255 ASCII printable chars, no whitespace) on every checkout call:

POST /v1/billing/crypto-checkout
Idempotency-Key: a1b2c3d4-5e6f-7890-1234-567890abcdef

A duplicate key returns the original order verbatim with an Idempotent-Replayed: 1 response header, for as long as the order row exists. A duplicate key with a different request body fires a structured crypto_checkout_idempotency_body_mismatch warn log; the contract still replays the original order, but operators can grep for accidental key reuse.

Pricing notes

• All amounts are in USD cents; NowPayments converts to crypto using their rate engine at the moment of payment_address mint.
• The pay_amount returned to your customer locks the exchange rate for the duration of the payment window (~20 minutes per NowPayments default). Outside that window the customer may need to re-create the order.
• Driftstack does not retain crypto; with NowPayments auto-conversion enabled (recommended) we receive USDT/EUR and the customer’s crypto exposure is eliminated on receipt.

Manual reconciliation

If an order is stuck (e.g., NowPayments IPN failed to deliver, customer reports payment but Driftstack shows pending), contact [email protected] with the order_id and the customer’s transaction hash. Manual replay is audit-logged and reflects the same crypto.order.paid webhook event your endpoint would have received on the original IPN.