Deposit Status Endpoint
Retrieve the status of a previously created deposit
Deposit Status
GET
https://api-stg.onekeypayments.com/v3/deposits/{deposit_id}
This endpoint allows you to retrieve the status of a deposit request.
Path Parameters
Name | Type | Description |
---|---|---|
deposit_id* | integer | Directa24 deposit_id. It is obtained when creating the deposit |
Headers
Name | Type | Description |
---|---|---|
X-Date* | string | ISO8601 Datetime with Timezone: |
X-Login* | string | Merchant X-Login API Key |
Authorization* | string | Authentication signature hash |
Request
You can trigger the check of the status of a deposit at any moment you consider pertinent. However, every time a deposit changes its status, we will send you a notification containing the ID of the deposit so that you can check its status back to retrieve the new deposit's status.
Example request
In the status endpoint, all the request have to be sent as GET, containing the usual headers.
Regarding the Authorization value, since the body of the requests will be empty, you should use an empty ("") string or nothing as the jsonPayload
field.
Example response
Response fields
Field name | Format | Description |
| String | ID generated for the user on OKP end |
| Number | ID of the deposit on OKP end |
| String | ID of the deposit on the merchant end |
| String | |
| String | |
| Number | Amount in local currency |
| Number | Amount in USD |
| Number | The amount specified as bonus in the request |
| Boolean | Specifies if the |
| String | Payment method code specified on the deposit request or selected by the user on our checkout. It will be shown only if the user has selected a payment method |
| String | Type of the payment method. It will be shown only if the user has selected a payment method |
| String | |
| Object | Object containing information about the payer. Only the values you've sent or we've collected will be shown. |
| String | Payer's document of identity |
| String | Payer's type of their document of identity |
| String | Payer's email |
| String | Payer's first name |
| String | Payer's last name |
| Object | Object containing the address details about the payer. Only the values you've sent or we've collected will be shown. |
| String | Payer's city |
| String | Payer's state ISO code |
| String | Payer's street |
| String | Payer's zip code |
| Number | Fee of the deposit in the currency of your balance. It will be shown only if the payment_method was sent by you or selected by the customer |
| String | Currency of your balance. It will be shown only if the payment_method was sent by you or selected by the customer |
| Object | Details about the bank account of the payer. This object is shown for all completed PIX transactions. |
| Number | Account number of the payer. |
| Number | Branch number of the payer (agencia). |
| Number | ISPB code of the payer's bank. |
| String | Name of the payer's bank. |
| String | Account type of the payer. Savings or Checking. |
| Object | Details about the credit card of the payer. This object will be shown only in case of credit card deposits and if we have the information. |
| String | Name of the card holder used to pay |
| String | Brand of the card used to pay |
| String | Masked card number used to pay |
| String | Expiration of the card used to pay in format YYYY-MM ( |
| String | Type of card used: CREDIT/DEBIT |
| String | The result message of the credit card transaction |
| Boolean | It shows if the deposit it was refunded or not. |
| String | It shows if the current payer is the same person who creates the deposit. It will be shown only if it is not null. |
payment_provider_reference | String | (Only for PSE deposits) Payment provider reference |
Parameter current_payer_verification
Through the parameter current_payer_verification you can check if the current payer is the same person who created the deposit. Below you can see the possible results for this parameter: Match --> The document of the person who paid is the same as the one of the person who created the payment. Unmatch --> The documents are different. No client document -> It is when there is no document of the person who proceed with the payment (Current payer). No current payer data -> It is when there is no document of the person who proceed with the payment (Current payer)
In order to make the experience more personalized, we may add more fields to this response's object in the future. Please develop your integration to be able to ignore new fields to avoid any issues.
If you are not sending all the payer details in the deposit request, make sure you store the details we collect and share with this endpoint so that in future attempts you can re-use them instead of having the payers to fill in the same details every time they deposit.
Status Flow
Click here to see each Deposit Status meaning.
Hosted Checkout Status Flow
OneShot Checkout Status Flow
The DECLINED status is not a status by itself. It means the transaction couldn't be created because of an error with the data, the customer or the merchant configuration. No transaction will change its status from DECLINED.
COMPLETED and CANCELLED* are final status.
*There are cases in which the users pays after the deposit expired, or paid an incorrect amount and the deposit gets expired. When that happens manual intervention is required to approve the deposit hence a deposit could change its status from EXPIRED or CANCELLED to COMPLETED.
EARLY RELEASED will only be used if you specified it in the deposit request.
FOR REVIEW is a transient status we use to specify that the deposit is under revision.
If the user doesn't pays, the transaction will be marked as EXPIRED. After 7 days it will change to CANCELLED.
Status codes
Check all the possible status in the following page:
API CodesLast updated