Skip to main content
POST
Poll a card purchase
Provider sandbox on this deployment. Our backend targets the card provider’s sandbox: no card is charged and no real transfer settles. Known limits: a purchase never reaches completed (it stops at processing), the settlement asset is the sandbox’s, not production’s (read cryptoCurrency from GET /v1/config), and the EUR window is unpublished (GET /v1/card/limits says window: unpublished). Every response says which environment answered in its environment field.

Authorizations

Authorization
string
header
required

Your API key, issued by us and shown once at creation.

Body

application/json
email
string
required

Buyer email from the card form.

Minimum string length: 1
Example:

"buyer@example.com"

transactionId
string
required
Minimum string length: 1
Example:

"txn_1"

Response

The purchase state.

environment
enum<string>
required

Which environment answered. sandbox: at least one money upstream is the provider's sandbox - no real money moves there, and the card corridor is the sandbox's asset (read GET /v1/config), not the documented production one. production: every configured upstream is real. Derived from the configured upstream hosts at boot, never a flag.

Available options:
sandbox,
production
Example:

"sandbox"

state
enum<string>
required

Normalized transaction state. NOTE: this field is named state here where every other product answers status.

Available options:
pending,
processing,
completed,
failed,
unknown
transactionId
string
required
deliveredAmount
string

Crypto actually delivered, as the provider's decimal STRING (up to 18 decimals). Absent until reported.

Example:

"0.058231428333752800"

deliveredCurrency
string

Currency of deliveredAmount.

Example:

"USDC"