Fiat (USD)
"Payments" vs "Transactions"
Two objects you'll see referenced many times in the APIs are the payment and transaction objects. These objects track the initiation of a movement of fiat/crypto and track the lifecycle of that movement. Most of your focus will be on the transaction object.
Payment:
- An object that tracks the initiation of a movement.
- If the initiation is successful, the payment is considered
completed
Transaction:
- An object that tracks the lifecycle of a particular movement
- The
statuswill change throughout the lifecycle, along with additional values being populated at certain
points. - This is the object you'll want to mainly track and for your system and your end users.
Below are the possible values for status related to the transaction object.
| Status | Operation | Description |
|---|---|---|
| New | ACH, Wires, Card Deposit | transaction is created, but not started yet |
| Processing | ACH, Wires, Deposit | transaction is processing, movement of fiat to destination account. |
| In Progress | ACH Deposit with ISA, Card Deposit | transaction is still in progress, only for card deposit, ACH deposit with ISA : waiting while compensation with ISA is finished |
| Failed | ACH, Wires, Card Deposit | transaction is failed, when the transaction failed at some stage: either on the card provider's/bank side or at settlement |
| Completed | ACH, Wires, Card Deposit | transaction is completed successfully, when the settlement/payment is completely finished |
All movements currently generate a
paymentandtransactionobjectInitiating a fiat movement (
payment), a crypto movement (transfer) or a crypto buy/sell (trade) will generate both apaymentobject as well as atransactionobject for tracking.
Updated about 23 hours ago