Deposit Status Endpoint

Retrieve the status of a previously created deposit

Deposit Status

GET https://api-stg.directa24.com/v3/deposits/{deposit_id}

This endpoint allows you to retrieve the status of a deposit request.

Path Parameters

Headers

{
    "user_id": "11",
    "deposit_id": 300004285,
    "invoice_id": "989409592",
    "country": "BR",
    "currency": "BRL",
    "local_amount": 53162.00,
    "usd_amount": 1000.00,
    "bonus_amount": 1.50,
    "bonus_relative": "false",
    "payment_method": "VI",
    "payment_type": "CREDIT_CARD",
    "status": "COMPLETED",
    "payer": {
        "document": "17532655253",
        "document_type": "CPF",
        "email": "johnSmith1@directa24.com",
        "first_name": "John",
        "last_name": "Smith",
        "address": {
            "city": "Sao Paulo",
            "state": "SP",
            "street": "John Street 2453",
            "zip_code": "938475-234"
        }
    },
    "fee_amount": 2.50,
    "fee_currency": "USD",
    "card_detail": {
        "card_holder": "John Smith",
        "brand": "Visa",
        "masked_card": "1234 56** **** 6789",
        "expiration": "2023-12",
        "card_type": "DEBIT",
        "transaction_result": "Transaction Approved"
    }
}

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.

curl --location --request GET 'https://api-stg.directa24.com/v3/deposits/300004285' \
--header 'X-Login: xxxxxxx' \
--header 'X-Date: 2020-06-24T17:13:21Z' \
--header 'Authorization: D24 e339247fb57b10c053159cf87d3a88415f9be567beb46a93f6839d9fc45d2c8a' \
--data-raw ''

Example response

{
    "user_id": "11",
    "deposit_id": 300004285,
    "invoice_id": "989409592",
    "country": "BR",
    "currency": "BRL",
    "local_amount": 53162.00,
    "usd_amount": 1000.00,
    "bonus_amount": 100.00,
    "bonus_relative": "false",
    "payment_method": "VI",
    "payment_type": "CREDIT_CARD",
    "status": "COMPLETED",
    "payer": {
        "document": "17532655253",
        "document_type": "CPF",
        "email": "johnSmith1@d24.com",
        "first_name": "John",
        "last_name": "Smith",
        "address": {
            "city": "Sao Paulo",
            "state": "SP",
            "street": "John Street 2453",
            "zip_code": "938475-234"
        }
    },
    "fee_amount": 2.50,
    "fee_currency": "USD",
    "refunded": False,
    "current_payer_verification": "UNMATCHED",
    "card_detail": {
        "card_holder": "John Smith",
        "brand": "Visa",
        "masked_card": "1234 56** **** 6789",
        "expiration": "2023-12",
        "card_type": "DEBIT",
        "transaction_result": "Transaction Approved"
    }
}

Response fields

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.

financial_institution Object

Example response with financial_institution object

{
    "deposit_id": 300852722,
    "invoice_id": "postmanTest295582678",
    "country": "BR",
    "currency": "BRL",
    "usd_amount": 188.33,
    "local_amount": 1000.00,
    "payment_method": "IX",
    "payment_type": "BANK_TRANSFER",
    "status": "COMPLETED",
    "payer": {
       "document": "17532655253",
       "document_type": "CPF",
       "email": "johnSmith1@d24.com",
       "first_name": "John",
       "last_name": "Smith",
       "address": {
           "city": "Sao Paulo",
           "state": "SP",
           "street": "John Street 2453",
           "zip_code": "938475-234"
        }
    },
    "fee_amount": 3.95,
    "fee_currency": "USD",
    "refunded": false,
    "current_payer_verification": "NO_CURRENT_PAYER_DATA",
    "completed_payment_method_code": "IX",
    "financial_institution": {
        "code": "33",
        "name": "BANCO SANTANDER (BRASIL) S.A.",
        "tax_identifier": "90.400.888/0001-42"
    }
}

bank_account Object

Pix example response with bank_account object

{
    "user_id": "11",
    "deposit_id": 300004285,
    "invoice_id": "989409592",
    "country": "BR",
    "currency": "BRL",
    "local_amount": 53162.00,
    "usd_amount": 1000.00,
    "bonus_amount": 1.50,
    "bonus_relative": "false",
    "payment_method": "VI",
    "payment_type": "CREDIT_CARD",
    "status": "COMPLETED",
    "payer": {
        "document": "17532655253",
        "document_type": "CPF",
        "email": "johnSmith1@directa24.com",
        "first_name": "John",
        "last_name": "Smith",
        "address": {
            "city": "Sao Paulo",
            "state": "SP",
            "street": "John Street 2453",
            "zip_code": "938475-234"
        }
    },
    "fee_amount": 2.50,
    "fee_currency": "USD",
    "bank_account": { 
        "account_number": "10122538", 
        "bank_branch": "90", 
        "ispb_code": 60746948,
        "bank_name": "Caixa",
        "account_type": "SAVING"
},
    }

SPEI example response with bank_account object

{
    "deposit_id": 704064213,
    "invoice_id": "MP_8112092e53f74ccaba16a8a1df37f7a7",
    "country": "MX",
    "currency": "MXN",
    "usd_amount": 2.18,
    "local_amount": 40.00,
    "payment_method": "SE",
    "payment_type": "VOUCHER",
    "status": "COMPLETED",
    "payer": {
        "document": "SSB190711FW6",
        "first_name": "JOHN SMITH"
    },
    "fee_amount": 2.18,
    "fee_currency": "USD",
    "refunded": false,
    "current_payer_verification": "UNMATCHED",
    "bank_account": {
        "bank_code": 12,
        "account_number": "012180001136299999"
    }
}

Status Flow

Click here to see each Deposit Status meaning.

Hosted Checkout Status Flow

OneShot Checkout Status Flow

  1. 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.

  2. COMPLETED and CANCELLED* are final status.

  3. *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.

  4. EARLY RELEASED will only be used if you specified it in the deposit request.

  5. FOR REVIEW is a transient status we use to specify that the deposit is under revision.

  6. 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:

Last updated