Retrieve Fiat Withdrawal
Endpoint that retrieves an specific Fiat Withdrawal given a fiat_withdrawal_id.
We offer the capability to set a Webhook URL in order to be notified in real time. Please note that you should expect a payload format similar to the one below. See IPN Webhooks in the documentation.
Authorizations
B2B’s White Label API uses OAuth2. Currently there is only one supported authentication flow:
- clientCredentials allows you to access your own B2B account (First-Party Integration) and performs transactions against the public API. This oauth2 flow is well suited for this API, as it allows machine-to-machine communication.
Every call to the API has to be authenticated with an OAuth2 Token. In order to request this token, you will need to have sandbox or production API Keys (client id and client secret) that will be needed to generate a credential in order to negotiate an ephemeral access token.
Every request must be accompianed by an Authorization
header with a value that follows the following schema: Bearer ACCESS_TOKEN
Path Parameters
Response
UUID used as fiat withdrawal identifier.
UUID used as fiat withdrawal's transaction identifier.
Indicates the fiat withdrawal creation date.
Indicates the fiat withdrawal's latest update date.
End user's external ref, usually a uuid. Identifies the user that owns this operation.
Indicates the asset name involved in the fiat withdrawal.
Indicates the fiat amount withdrawed.
Specifies the fiat withdrawal status.
PENDING
, COMPLETED
, CANCELLED
Client side identification reference. Usually a UUID.
128
UUID used as beneficiary fiat account identifier.
Shows if the fiat withdrawal corresponds to the refund of a fiat deposit.
UUID from a refunded fiat deposit, it could be null.