Skip to content

Integrating Afterpay

Auth: API key · Partner program: not required · Setup time: about 10 minutes · Last verified: 2026-05-15

BNPL in the US, Australia, and New Zealand — Pay-in-4 and Pay Monthly. Block-owned (parent of Cash App).

raw is opt-in. The upstream payload is withheld unless an operator enables data_store.raw_payload.payments in Admin → Settings → Data store. It is off by default because across the payments adapters it declares bank account numbers, IBANs and card numbers the canonical schema does not expose.

HTTP Basic from merchantId:secretKey. Region-specific hosts:

  • US: api.us-sandbox.afterpay.com / api.us.afterpay.com
  • AU/NZ: api-sandbox.afterpay.com / api.afterpay.com

Sandbox credentials are generated through the Cash App developer portal (Afterpay’s sandbox lives under the broader Cash App developer tooling); live keys come from the Afterpay merchant dashboard.

  • Same installments-vs-principal model as Klarna and Affirm — Charge.amount is the order principal; installment schedule lives in raw.
  • Capture is required. Afterpay authorises at customer-confirm time, but merchants must explicitly call captureCharge (defer-shipping flow) before the auth expires (~24h depending on region).
  • requestId idempotency. Every refund needs a unique request ID; the adapter generates oi-<timestamp> automatically.

Configure in the merchant dashboard. HMAC-SHA-256 of the raw body keyed with the configured secret, hex-encoded in Signature.