Your product.
One operational layer.
Separate the customer interface from transaction logic. Define request formats, statuses, error handling and reconciliation procedures in advance.
○ ○ ○ payment.example.jsonCONCEPT
{ "type": "payment_request", "asset": "STABLECOIN", "amount": "100.00", "reference": "invoice_001", "status": "awaiting_confirmation", "environment": "illustrative" }
Illustrative data model. Not a live API.
Idempotency
A repeated request should not unintentionally repeat a financial operation.
Events and statuses
Agree on state transitions and handling for duplicate or delayed events.
Errors and recovery
Distinguish validation errors, restrictions, temporary failures and uncertain outcomes.
Illustrative payment states
| State | Meaning | Interface action |
|---|---|---|
| created | Request prepared | Display details and terms |
| pending | Awaiting confirmation | Show processing progress |
| completed | Transaction confirmed | Display the result and receipt |
| failed | Transaction incomplete | Explain the reason and next step |
A live API, SDK, sandbox, access keys and specification have not yet been published. Field and state names are illustrative only.