SaaS

Invoices and links for recurring revenue.

For subscription and usage-based businesses: issue an invoice per billing period or share a payment link. Each payment is tied to its own invoice and checkout session, so matching is never a guess.

Workflow

How it runs, step by step.

  1. Your billing

    Period closes

    Create an invoice with line items, a customer reference and an expiry.

    POST /v1/invoices
  2. Customer

    Pays the invoice

    The invoice link opens the hosted checkout with the amount fixed in your currency.

    checkout_url
  3. GRYPHEM

    Confirmation

    The payment is matched to this invoice alone; once it confirms, the invoice status follows the payment.

    invoice → paid
  4. Your billing

    Mark period paid

    The signed webhook updates the subscription. Reports and CSV exports feed revenue recognition.

    payment.confirmed

Outcomes

What changes for your team.

  • One payment, one invoice

    Every payment is tied to its own invoice and checkout session, so payments match without heuristics.

  • Payment links for top-ups

    Reusable links create a fresh payment intent per visit — useful for credits, deposits or one-off upgrades.

  • Finance-ready exports

    CSV exports carry UTC timestamps, transaction hashes and the credited amount for every payment.

  • Fees billed, not skimmed

    Platform fees are invoiced to you monthly and never deducted from customer payments.

Before you integrate

Things to decide up front.

  • Crypto has no pull payments: customers must send each payment. Plan reminders before invoices expire.
  • Price in your fiat currency; the asset amount is fixed only when the customer opens the checkout.
  • Decide how long an invoice stays payable and what happens to payments that arrive after expiry.
  • Keep usage metering on your side authoritative; GRYPHEM PAY confirms payments, not entitlements.