Retrieve payment list of an order
Retrieve a list of payments for a specific order, based on the order's ID.
This endpoint is part of a new API, pay attention to the different endpoint URL.
Use this endpoint to retrieve payment details for saved payment methods to make merchant and customer initiated transactions. For more information, see:
Request
The ID of the Order object.
Example: "Bearer sk_1234567890ABCdefGHIjklMNOpqrSTUvwxYZ_1234567890-Ab_cdeFGHijkLMNopq"
This parameter accepts the Merchant API Secret key to authorise requests coming from the merchant's backend.
It ensures that ensures that each request is authenticated and authorised by verifying the secret key. The secret key should be included in all request headers as a Bearer token.
For more information, see: Authentication
Response
List of payments
The ID of the payment.
Permanent order ID used to retrieve, capture, cancel, or refund an order after authorization.
The payment method used to pay for the order.
Possible values: [card, revolut_pay]
The type of payment method used to pay for the order.
Possible values: [revolut_account, card]
Indicates whether the customer used their card or Revolut account via Revolut Pay.
ID of the saved payment method.
The id parameter is only returned if the payment method is saved.
Temporary token of the payment used to fetch the reward offer during checkout and link user registrations to the given offers.
The token is only valid for a limited time.
Example: 600
The payment amount in minor units (e.g., cents). The value of this field depends on the payment type and state.
| Payment type | State | Amount value |
|---|---|---|
| Standard payment | Any | Total payment amount |
| Pre-authorised payment | authorisation_started | New amount being authorised (during increment processing) |
| Pre-authorised payment | authorised | Currently authorised amount (equals authorised_amount) |
For pre-authorised payments, see the authorised_amount field for tracking the currently authorised amount separately.
Possible length: >= 3 characters and <= 3 characters
ISO 4217 currency code in upper case.
For more information about the supported currencies, see: Help Center.
Possible values: [pending, authentication_challenge, authentication_verified, authorisation_started, authorisation_passed, authorised, capture_started, captured, refund_validated, refund_started, cancellation_started, declining, completing, cancelling, failing, completed, declined, soft_declined, cancelled, failed]
The status of the payment.
Possible values: [3ds_challenge_abandoned, 3ds_challenge_failed_manually, cardholder_name_missing, customer_challenge_abandoned, customer_challenge_failed, customer_name_mismatch, do_not_honour, expired_card, high_risk, insufficient_funds, invalid_address, invalid_amount, invalid_card, invalid_country, invalid_cvv, invalid_email, invalid_expiry, invalid_merchant, invalid_phone, invalid_pin, issuer_not_available, pick_up_card, rejected_by_customer, restricted_card, suspected_fraud, technical_error, transaction_not_allowed_for_cardholder, unknown_card, withdrawal_limit_exceeded]
The reason for a failed or declined payment.
A failed or declined payment can result from multiple reasons. To learn more, check our failure reasons.
Details about the authentication challenge that should be performed to complete the authentication process. For more information about Revolut's 3DS solution, see: 3D Secure overview.
Only returned if the payment's state is authentication_challenge.
Information about the 3DS challenge.
Possible values: [three_ds, three_ds_fingerprint]
Type of the authentication challenge the payment triggers.
The URL of the authentication challenge.