Finalized Event Transaction Details
Following the final result of a 3D Secure transaction, whether the authentication is frictionless, SMS, SMS & Knowledge Based Authentication (KBA) or Out of Band (OOB), CLOWD9 will communicate the outcome to you.
Transaction Details:
Field Name | Description | Format | Mandatory |
|---|---|---|---|
client_id | Client identifier in UUID | String | Yes |
card_id | The UUID of the card relating to the purchase | String | Yes |
customer_id | The UUID of the Customer | String | Yes |
sp_transaction_id | Apata transaction ID | String | Yes |
ds_transaction_id | Directory server unique transaction id | String | No |
card_acceptor_id | The ID of the merchant | String | Yes |
card_acceptor_name | The Merchant name | String | Yes |
card_acceptor_country | The Merchant's country | String | Yes |
transaction_category | Type of transaction for which authentication is requested. Values are: “payment” - Spend | String | Yes |
transaction_currency_code | Numeric ISO currency code of the transaction | String | Yes |
transaction_currency_exponent | Minor units of the transaction currency | String | Yes |
transaction_amount | Transaction amount in minor units of the transaction currency | String | Yes |
transaction_channel | Channel at which transaction was acquired through. Values are: "app" - A mobile app | String | No |
challenge_method | Method of challenge. Values are: PUSH_CONFIRMATION | String | Yes |
transaction_status | Status of the transaction. Values are: RBA_ACCEPTED | String | Yes |
transaction_datetime | Date & Time of the transaction | Integer | Yes |
challenged_datetime | Date and time when the end user was challenged | Integer | Only for OOB |
challenge_expiry_window | Time window until the challenge is valid from challenged_datetime | Integer | Only for OOB |
challenge_expiry_datetime | Date and time when the challenge expires | Integer | Only for OOB |
Example:
{
"client_id" : "",
"card_id" : "",
"customer_id" : "",
"sp_transaction_id" : "",
"ds_transaction_id" : "",
"card_acceptor_id" : "",
"card_acceptor_name" : "",
"card_acceptor_country" : "",
"transaction_category" : "",
"transaction_currency_code" : "",
"transaction_currency_exponent" : "",
"transaction_amount" : "",
"transaction_channel" : "",
"transaction_datetime" : "",
"challenge_datetime" : "",
"challenge_expiry_window" : "",
"challenge_expiry_datetime" :"",
}Transaction Details Response:
| client_id | Client identifier in UUID |
|---|---|
| card_id | The UUID of the card relating to the purchase |
| customer_id | The UUID of the Customer |
| sp_transaction_id | Apata transaction ID |
| status | Status of the web hook request. Should carry a static value of “ok” |
Example:
{
"client_id" : "",
"card_id" : "",
"customer_id" : "",
"sp_transaction_id" : "",
"status" : "ok"
}Updated about 1 month ago