List Payments
GET/payments
List Payments
Request
Query Parameters
Default value: 1
Page to list
Payment ID to look for
Possible values: [initiated
, paid
, authorized
, failed
, refunded
, captured
, voided
, verified
]
Status to filter by
Filter payments equal or greater than a give date
Filter payments equal or less than a give date
Filter payments updated on a given date or later
Filter payments updated on a given date or prior
Filter invoices by a given metadata key
. You need to change in the key in the square brackets.
Possible values: Value must match regular expression ^\d{4}$
Filter payments by card last digits.
Only available for scheme payments: creditcard
, applepay
, samsungpay
, googlepay
.
Possible values: Value must match regular expression ^\d{12}$
Filter payments by RRN or retreival reference number.
Responses
- 200
- 401
- 403
- application/json
- Schema
- Example (from schema)
Schema
Array [
- CreditCardResponse
- ApplePayResponse
- GooglePayResponse
- SamsungPayResponse
- StcPayResponse
- Apple Pay:
ap
- Samsung Pay:
sp
- Google Pay:
gp
- Apple Pay:
ap
- Samsung Pay:
sp
- Google Pay:
gp
- Apple Pay:
ap
- Samsung Pay:
sp
- Google Pay:
gp
]
paymentsobject[]
Possible values: [initiated
, paid
, authorized
, failed
, refunded
, captured
, voided
, verified
]
Indicates the payment status.
If the payment is in the initiated
status, then an action must be taken (e.g. 3DS challenge) in order to
complete the payment.
The status authorized
is used when a scheme payment is made with manual: true
option which will cause
the system to authorize the payment only without capturing it. The merchant must capture the payment within
time it will be voided automatically by the issuer. Please note that when an issuer voids the payment, the
status will be kept authorized
and WILL NOT BE updated by the system.
Estimated payment fee (including VAT).
ISO-4217 three-letter currency code.
Refunded amount. Less than or equal to the payment amount.
Captured amount. Less than or equal to the payment amount.
Formatted payment amount with currency
Invoice ID that this payment is used to pay.
Payer IPv4 address. This information is collected from the connection that has created the payment.
You must ensure that the payment is created from the client device directly to ensure correct collection of the IP address.
metadataobject
A set of key-value pairs where both key and value are strings. Metadata allows you to add more information to the object that will be returned later on in responses and webhook messages. Metadata is searchable using the Payment List API.
sourceobjectrequired
Source response object
oneOf
Possible values: [creditcard
]
Possible values: [mada
, visa
, master
, amex
]
The scheme through which the payment is processed.
Card holder name
Masked card number showing first six and last four digits.
ID used for the backing acquirer gateway (MPG, MPGS or Cybersource).
Token that is created using this payment.
Human readable string representing the transaction result.
3D Secure challenge URL. Only returned when payment is initiated
.
Possible values: Value must match regular expression ^\d{12}$
The RRN or retrieval reference number. This is a unique number for the transaction generated by the acquirer gateway and is sent to the issuer during the authorization process.
This number is not unique across schemes (e.g. Visa and mada).
This number can be useful in tracking the payment in the card holder account statement.
Possible values: Value must match regular expression ^\d{6}$
A six-digit number returned by the issuer in response to a successful authorization process.
A two-digit string representing the authorization result (ISO 8583).
Response code 00
indicates that the payment is approved by the issuer. Please refer to the response code table
in the documentation for more information.
Name of the card issuing bank. This name is inferred based on the card BIN or IIN.
Origin country of the card issuer. A two-letter ISO 3166 code.
Possible values: [debit
, credit
, charge_card
, unspecified
]
Indicates the card category or product type, e.g., Platinum, Signature, etc.
This field is a human readable text and does not have a defined set of values.
Possible values: [applepay
]
Name will always be null
for Apple Pay payments.
Possible values: [mada
, visa
, master
, amex
]
The scheme through which the payment is processed.
Masked card number showing only last four digits.
Masked card number showing first six and last four digits.
ID used for the backing acquirer gateway (MPG, MPGS or Cybersource).
The xx
part is different based on the payment source:
Possible values: Value must match regular expression ^\d{12}$
The RRN or retrieval reference number. This is a unique number for the transaction generated by the acquirer gateway and is sent to the issuer during the authorization process.
This number is not unique across schemes (e.g. Visa and mada).
This number can be useful in tracking the payment in the card holder account statement.
Human readable string representing the transaction result.
A two-digit string representing the authorization result (ISO 8583).
Response code 00
indicates that the payment is approved by the issuer. Please refer to the response code table
in the documentation for more information.
Possible values: Value must match regular expression ^\d{6}$
A six-digit number returned by the issuer in response to a successful authorization process.
Name of the card issuing bank. This name is inferred based on the card BIN or IIN.
Origin country of the card issuer. A two-letter ISO 3166 code.
Possible values: [debit
, credit
, charge_card
, unspecified
]
Indicates the card category or product type, e.g., Platinum, Signature, etc.
This field is a human readable text and does not have a defined set of values.
Possible values: [googlepay
]
Name will always be null
for Apple Pay payments.
Possible values: [mada
, visa
, master
, amex
]
The scheme through which the payment is processed.
Masked card number showing only last four digits.
Masked card number showing first six and last four digits.
ID used for the backing acquirer gateway (MPG, MPGS or Cybersource).
The xx
part is different based on the payment source:
Possible values: Value must match regular expression ^\d{12}$
The RRN or retrieval reference number. This is a unique number for the transaction generated by the acquirer gateway and is sent to the issuer during the authorization process.
This number is not unique across schemes (e.g. Visa and mada).
This number can be useful in tracking the payment in the card holder account statement.
Human readable string representing the transaction result.
A two-digit string representing the authorization result (ISO 8583).
Response code 00
indicates that the payment is approved by the issuer. Please refer to the response code table
in the documentation for more information.
Possible values: Value must match regular expression ^\d{6}$
A six-digit number returned by the issuer in response to a successful authorization process.
Name of the card issuing bank. This name is inferred based on the card BIN or IIN.
Origin country of the card issuer. A two-letter ISO 3166 code.
Possible values: [debit
, credit
, charge_card
, unspecified
]
Indicates the card category or product type, e.g., Platinum, Signature, etc.
This field is a human readable text and does not have a defined set of values.
Possible values: [samsungpay
]
Name will always be null
for Apple Pay payments.
Possible values: [mada
, visa
, master
, amex
]
The scheme through which the payment is processed.
Masked card number showing only last four digits.
Masked card number showing first six and last four digits.
ID used for the backing acquirer gateway (MPG, MPGS or Cybersource).
The xx
part is different based on the payment source:
Possible values: Value must match regular expression ^\d{12}$
The RRN or retrieval reference number. This is a unique number for the transaction generated by the acquirer gateway and is sent to the issuer during the authorization process.
This number is not unique across schemes (e.g. Visa and mada).
This number can be useful in tracking the payment in the card holder account statement.
Human readable string representing the transaction result.
A two-digit string representing the authorization result (ISO 8583).
Response code 00
indicates that the payment is approved by the issuer. Please refer to the response code table
in the documentation for more information.
Possible values: Value must match regular expression ^\d{6}$
A six-digit number returned by the issuer in response to a successful authorization process.
Name of the card issuing bank. This name is inferred based on the card BIN or IIN.
Origin country of the card issuer. A two-letter ISO 3166 code.
Possible values: [debit
, credit
, charge_card
, unspecified
]
Indicates the card category or product type, e.g., Platinum, Signature, etc.
This field is a human readable text and does not have a defined set of values.
Possible values: [stcpay
]
Mobile number used to authorize the STC Pay payment.
Authorization attempt reference number returned by the STC Pay service.
Cashier identifier sent to STC Pay during request initiation. This will show in the merchant dashboard.
Branch identifier sent to STC Pay during request initiation. This will show in the merchant dashboard.
OTP challenge URL.
You must collect the OTP value from the user and make POST
request to the URL returned here along
with the OTP value in a parameter called: otp_value
.
Human readable string representing the transaction result.
metaobject
{
"payments": [
{
"id": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
"status": "initiated",
"amount": 100,
"fee": 0,
"currency": "SAR",
"refunded": 0,
"refunded_at": "Date and time when the payment was refunded.",
"captured": 0,
"captured_at": "Date and time when the payment was captured.",
"voided_at": "Date and time when the payment was voided.",
"description": "Kindle Whitepaper",
"amount_format": "1.00 SAR",
"fee_format": "0.00 SAR",
"refunded_format": "0.00 SAR",
"captured_format": "0.00 SAR",
"invoice_id": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
"ip": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
"callback_url": "https://example.com/checkout/payer-return",
"created_at": "Date and time when the payment was created.",
"updated_at": "Date and time when the payment was last updated.",
"metadata": {
"cart_id": "72e470a5-cbc4-47b3-a52a-e89fda6adb19",
"customer_email": "[email protected]",
"customer_id": "23432"
},
"source": {}
}
],
"meta": {
"current_page": 1,
"next_page": null,
"prev_page": null,
"total_pages": 1,
"total_count": 1
}
}
- application/json
- Schema
- Example (from schema)
Schema
Possible values: [authentication_error
]
Possible values: [Invalid authorization credentials
]
{
"type": "authentication_error",
"message": "Invalid authorization credentials",
"errors": null
}
- application/json
- Schema
- Example (from schema)
Schema
Possible values: [api_error
]
Possible values: [User not authorized
]
{
"type": "api_error",
"message": "User not authorized",
"errors": null
}