Skip to main content
POST
Where a submitted deposit is by receipt
Production, real money. This endpoint runs on live routes: the transaction you build moves real funds the moment the user signs it, and every hash you see is a real one. There is no crypto sandbox. Use a small amount to try it.

Authorizations

Authorization
string
header
required

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

Body

application/json
provider
string
required

The provider from the quote.

Example:

"lifi-aggregator"

receipt
object
required
quote
object
required

The quote this transfer was built from, unchanged. On /v1 the quote is the credential that proves the transfer is yours; a status read is answered even after the quote's price deadline has passed.

Response

The transfer status.

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"

status
enum<string>
required

pending: in flight. done: delivered (credit the user). failed: broke, nothing delivered. refunded: the money went back to the sender. expired: produced by no provider today, kept for older consumers. unknown: the provider answered a word outside this vocabulary (see providerStatus) - not terminal, poll again.

Available options:
pending,
done,
failed,
expired,
refunded,
unknown
providerStatus
string

The provider's own status word, verbatim - present only when status is unknown.

txHashes
object
deliveredAmount
string

What the destination transaction actually paid out, as a decimal string in the token's MAJOR unit (e.g. "100.134221"). Absent until reported. This is the figure to reconcile against; the quote's outAmount is a floor.

Example:

"100.134221"