WithdrawalInformation
Withdrawal id generated during creation.
5000000123
1000000123
2000000123
Slip identifier. Slip contains list of transactions associated with the withdrawal operations.
5009964049
Withdrawal funding transaction id.
544232
Represents RFC 3339, section 5.6 date-time.
2021-07-15T17:54:12Z
The payment status:
PREVIEW
- Payment preview.PENDING
- Payment transaction is created and further action is required by the customer.PROCESSING
- Payment is scheduled for processing by the payment provider.COMPLETED
- Payment is completed. Note that some transactions might be completed from Embedded Wallet point of view, but not from customer point of view, since money movement might take some time outside of the Embedded Wallet network.FAILED
- Payment has failed. Check STATUS_REASON property for details.CANCELLED
- Payment have been cancelledREFUNDED
- Payment has been refunded. Valid only for deposits.
Possible values: [PREVIEW
, PENDING
, PROCESSING
, COMPLETED
, FAILED
, CANCELLED
, REFUNDED
]
COMPLETED
Status reason for FAILED transaction.
Possible values: <= 60 characters
Provides the next possible status update the client can request, depending on the chosen payment type and option.
Possible values: [PREVIEW
, PENDING
, PROCESSING
, COMPLETED
, FAILED
, CANCELLED
, REFUNDED
]
Specifies action required to complete to be able to continue to the next payment status:
NONE
– No action is required, you can proceed to the next deposit status.REDIRECT
– The user must be redirected in order to complete a payment, for example, when an alternate payment method like Paysafecard is used.SCA
- The user must complete a Strong Customer Authentication (SCA) process.
Possible values: [NONE
, REDIRECT
, SCA
]
NONE
NONE
scaDetails object
SCA authentication details, including information about the authentication process. It should be present in the response of any wallet operation that requires it due to PSD2 regulatory requirements.
- Present in the response - operation requires SCA authentication, and the user should proceed with the SCA process.
- Not present in the response - operation does not require SCA authentication and is authorized to proceed.
The distinct identifier for the SCA authentication event.
06bdcd2c-0cce-4b36-97ec-281c8f5d743c
The distinct identifier for the wallet operation. This identifier is used to associate the wallet operation with the SCA authentication event.
a5865fd6-18c2-45a8-9953-1c00eac36c36
Mode of the Strong Customer Authentication (SCA) authentication process.
OUTSOURCED
- The partner is responsible for handling the entire SCA process.EMBEDDED
- Paysafe is responsible for handling the entire SCA process, including user authentication and compliance with regulations like PSD2.HYBRID
- Paysafe manages the entire SCA process, excluding the communication with the end-user.
Possible values: [OUTSOURCED
, EMBEDDED
, HYBRID
]
OUTSOURCED
List of available verifications for the SCA authentication event. If none are specified, the user can proceed with any agreed-upon verification method.
Represents RFC 3339, section 5.6 date-time.
2021-07-15T17:54:12Z
Enumeration of supported Payment Option Types
Possible values: [RAPID_TRANSFER
, BANK_TRANSFER
, OFFLINE_BANK_TRANSFER
, CARD
, PAYSAFECASH
, PAGO_EFECTIVO
]
CARD
{
"id": "5000000123",
"accountId": "1000000123",
"customerId": "2000000123",
"slipId": "5009964049",
"fundingTransactionId": "544232",
"creationTime": "2021-07-15T17:54:12Z",
"expirationTime": "2021-07-15T17:54:12Z",
"status": "COMPLETED",
"statusReason": "string",
"nextStatus": [
"COMPLETED"
],
"action": "NONE",
"scaDetails": {
"eventId": "06bdcd2c-0cce-4b36-97ec-281c8f5d743c",
"walletOperationId": "a5865fd6-18c2-45a8-9953-1c00eac36c36",
"authenticationMode": "OUTSOURCED",
"availableVerifications": [
{
"method": "OTP",
"channel": "SMS",
"target": "jo***@example.com"
}
],
"creationTime": "2021-07-15T17:54:12Z",
"expirationTime": "2021-07-15T17:54:12Z"
},
"paymentOption": "CARD"
}