Fetch Payment Source
GET/payments/:id/source
Fetch the extended source object for a payment. In addition to the standard source fields, this returns operational details that are not part of a normal payment response — acquirer references, terminal, gateway, reconciliation date, and the network (scheme) transaction IDs for the authorization/purchase, capture, void, and refund. The response shape depends on the payment's source type.
Request
Path Parameters
ID of the payment whose source to fetch
Responses
- 200
- 401
- 403
- 404
Successful operation
- application/json
- Schema
Schema
- CreditCardExtendedResponse
- ApplePayExtendedResponse
- SamsungPayExtendedResponse
- StcPayExtendedResponse
- Apple Pay:
ap - Samsung Pay:
sp - Apple Pay:
ap - Samsung Pay:
sp
oneOf
Possible values: [creditcard]
Possible values: [mada, visa, master, amex, unionpay]
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.
Acquirer terminal ID used for the transaction.
Backing acquirer gateway that processed the transaction.
Acquirer reconciliation (settlement) date.
Machine-readable failure reason when the transaction failed.
Acquirer reference for the refund operation.
Acquirer reference for the void operation.
Acquirer reference for the capture operation.
Network (scheme) transaction ID for the authorization/purchase.
Network (scheme) transaction ID for the refund.
Network (scheme) transaction ID for the void.
Network (scheme) transaction ID for the capture.
Statement descriptor sent to the issuer for the transaction.
Possible values: [applepay]
Name will always be null for Apple Pay payments.
Possible values: [mada, visa, master, amex, unionpay]
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.
Token that is created using this payment.
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.
Acquirer terminal ID used for the transaction.
Backing acquirer gateway that processed the transaction.
Acquirer reconciliation (settlement) date.
Machine-readable failure reason when the transaction failed.
Acquirer reference for the refund operation.
Acquirer reference for the void operation.
Acquirer reference for the capture operation.
Network (scheme) transaction ID for the authorization/purchase.
Network (scheme) transaction ID for the refund.
Network (scheme) transaction ID for the void.
Network (scheme) transaction ID for the capture.
Possible values: [samsungpay]
Name will always be null for Apple Pay payments.
Possible values: [mada, visa, master, amex, unionpay]
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.
Token that is created using this payment.
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.
Acquirer terminal ID used for the transaction.
Backing acquirer gateway that processed the transaction.
Acquirer reconciliation (settlement) date.
Machine-readable failure reason when the transaction failed.
Acquirer reference for the refund operation.
Acquirer reference for the void operation.
Acquirer reference for the capture operation.
Network (scheme) transaction ID for the authorization/purchase.
Network (scheme) transaction ID for the refund.
Network (scheme) transaction ID for the void.
Network (scheme) transaction ID for the capture.
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.
Possible values: [void, refund]
The kind of reversal applied to the payment, if any.
When the payment was reversed, if it was.
Invalid authorization credentials
- 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
}
Invalid authorization credentials
- 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
}
One of the record referenced in the request was not found
- application/json
- Schema
- Example (from schema)
Schema
Possible values: [record_not_found]
{
"type": "record_not_found",
"message": "The <object type> record you were looking for was not found.",
"errors": null
}