Developers
Three ways in. Card data never touches your servers in any of them.
At a glance
- Protocol
- REST, JSON
- Auth
- Per-account API keys
- Card capture
- Hosted fields, tokenized
- Events
- Signed webhooks, replayable
- Sandbox
- Unlimited, production parity
Reviewed
Three ways in
Pick the one that matches your team.
Hosted checkout
No codeMost merchants
A payment page we host and secure, styled to your brand. Cards, ACH and wallets on one page. You link to it or embed it; we handle the card data, 3-D Secure and the receipt. PCI scope stays at the lightest self-assessment because nothing sensitive ever reaches your systems.
- Brandable — your logo, colors and domain
- Cards, ACH and wallets on one page
- 3-D Secure and fraud rules applied server-side
- Payment links for phone, email and text
Card data is tokenized in the browser. It never reaches the merchant.
Cart plugins
Plugin installExisting stores
Drop-in support for the major cart platforms, so a store that already exists moves without being rebuilt. The plugin uses hosted fields under the hood, so the PCI position is the same as hosted checkout.
- Major platforms supported
- Keeps your existing catalog and order flow
- Hosted fields — card data bypasses your server
- Same dashboard and reporting as every other channel
Amount
$1,250.00
REST API and hosted fields
Engineering time, scope-dependentTeams with engineers
A documented REST API for charges, refunds, customers, subscriptions, payouts and disputes. Hosted fields you embed in your own pages tokenize card data before it touches your code. Signed webhooks for every event, replayable from the dashboard. The sandbox is unlimited and identical to production except for the keys.
- Charges, refunds, customers, subscriptions, payouts, disputes
- Hosted fields for tokenized card capture in your own UI
- Signed webhooks with retry and replay
- Idempotency keys on every write
- Unlimited sandbox, production parity
Signed, retried with backoff, replayable from the dashboard.
Where card data goes
Your server only ever sees a token.
Cardholder's browser
Types the card number
Hosted field
Served by us, inside your page
Token
Stands in for the card
Your server
Never holds the card number
Dash platform
Authorizes, captures, settles
The full statement of where card data, documents and money go is on Security & trust.
Webhooks
Every event that matters, delivered to your system.
- payment.succeeded
- A charge was captured and will settle
- payment.failed
- Declined or errored, with the reason code
- refund.completed
- A refund posted back to the customer
- settlement.posted
- A batch settled to your account, with the fee breakdown
- payout.sent
- An outbound payout left the platform
- dispute.opened
- A chargeback or pre-dispute alert was raised
- dispute.resolved
- Won, lost, or refunded before it posted
- reserve.released
- Reserve funds aged past term and released
Signed, retried with backoff, replayable from the dashboard.
Sandbox
Request sandbox access.
Issued by a person
Credentials come from a person, not a queue. Nothing to sign first.
Production parity
Same API, same webhooks, same dashboard. Only the keys change when you go live.
The reference that fits you
You get the endpoints for the products in scope, not a catalog of things your account cannot use.
Questions
From engineers.
Start with the sandbox, or with the file.
Engineers can have credentials now. Merchants can find out which acquiring partner writes the category before anyone writes a line of code.