Get a payment
GEThttps://app.shuttleglobal.com/c/api/instances/{instance_key}/payments/{payment_id}
Retrieve details of a specific payment. You can expand additional related objects using the expand parameter.
Available expand options:
- contract
- transaction
- parts
- payment_method
Authorizations
Section titled “Authorizations”Parameters
Section titled “Parameters”Path Parameters
Section titled “Path Parameters”The payment’s ID (pay_...), capture ID (ca_...) or transaction ID (tr_...), or the alt_key you gave it (case-insensitive).
An ID must be for a payment, capture or authorisation, otherwise 404 Payment not found.
An alt_key returns the newest record with that key.
Query Parameters
Section titled “Query Parameters”Related objects to include in the response
Responses
Section titled “Responses”Payment details
object
Payment details
object
"pay_11842_10000"Payment identifier
"1234"Your supplied payment reference
"Invoice 1234"Payment description
"MOTO"Payment source
"PAYMENT"Payment action type
"SUCCESS"The status of the payment:
- SUCCESS - The payment was approved
- PENDING - The payment is still in progress
- DECLINED - The payment was declined
- REQAUTH - The payment requires authorization step (e.g. 3D secure)
- INVALID_PAYMENT_METHOD - Invalid payment method used
- UNRESOLVED - No conclusive approval/decline received
- UNATTRIBUTED - Success but internal recording issue
"APPROVED"Category or error message from the gateway
"ch_1GVaEEFi2CnH4uN3ouw69fw3"Gateway’s identifier for the transaction
"pi_1GVaEEFi2CnH4uN355ZdZvk5 (TEST)"Authorization code from the gateway
"REF-00010000"Customer-facing reference (e.g., BOLT-123445)
"100"Payment amount
"100"Payment amount less any refunds
"GBP"Payment currency in ISO format
When the payment was resolved
"CUSTOMER_ACTION_REQUIRED"Sub-status of the payment, present when the gateway is waiting for someone to act. CUSTOMER_ACTION_REQUIRED means the customer still has something to do - e.g. a bank transfer or Multibanco payment stays PENDING until they make the transfer or pay the voucher. MERCHANT_ACTION_REQUIRED is reserved for future use. Omitted and NO_ACTION_REQUIRED mean the same thing.
"follow_bank_transfer_instructions"Free-text description of the sub-status, e.g. follow_bank_transfer_instructions, follow_voucher_instructions or partially_funded. Descriptive only - not searchable.
"2020-04-13T00:00:00.000Z"Intended payment date. Present only when the payment was created ahead of its target date because the payment method requires gateway advance notice (e.g. SEPA/BACS/GoCardless/Stripe ACH). This is the target date, not the settlement date, and is omitted for payment methods that charge on the due date.
"GBP"Settlement currency if different from transaction currency
"100"Gross amount in settlement currency
"96.9"Net amount in settlement currency after fees
"3.1"Processing fees in settlement currency
"gw_11842_10000"Gateway used for processing
"acc_11842_10000"Associated account ID
"pm_11842_10000"Payment method ID used
"co_11842_10000"Associated contract ID
"ch_11842_10001"Processing channel
"in_11842_10000"Initiative ID
"des_11842_10000"Designation ID
"le_11842_10000"Legal entity ID
"2020-04-08T09:29:48.000Z"Creation timestamp
"2020-04-08T09:29:52.000Z"Last update timestamp
"2020-04-08T09:29:51.000Z"Processing timestamp
Gateway-specific data (varies by gateway)
object
falseWhether a tokenized payment method was used
falseWhether this is a recurring payment
"MONTHLY"Frequency for recurring payments
12Number of planned occurrences for recurring payments
"212.161.80.4"IP address of the browser that initiated the payment
Associated contract details
object
"co_11842_10000"Contract identifier
"acc_11842_10000"Associated account ID
"1234"Your reference for this contract
"100"Contract amount
"GBP"Contract currency
"Invoice 1234"Contract description
"COMPLETED"Status of the contract
falseWhether this is a recurring contract
"pm_11842_10000"Payment method ID used
"2020-04-08T09:29:48.000Z"Creation timestamp
"2020-04-08T09:29:52.000Z"Last update timestamp
"2020-04-08T09:29:48.000Z"Initiation timestamp
"2020-04-08T09:29:52.000Z"Completion timestamp
"tr_11842_10000"The last transaction ID for this contract
Frequency for recurring contracts
Number of planned occurrences for recurring contracts
Next scheduled charge date for recurring contracts
Number of charges processed for this contract
Transaction details
object
"tr_11842_10000"Transaction identifier
"PAYMENT"Transaction action type
"MOTO"Transaction source
"SUCCESS"Transaction status
"APPROVED"Status reported by the gateway
"CUSTOMER_ACTION_REQUIRED"Sub-status of the transaction, present when the gateway is waiting for someone to act. CUSTOMER_ACTION_REQUIRED means the customer still has something to do - e.g. a bank transfer or Multibanco payment stays PENDING until they make the transfer or pay the voucher. MERCHANT_ACTION_REQUIRED is reserved for future use. Omitted and NO_ACTION_REQUIRED mean the same thing.
"follow_bank_transfer_instructions"Free-text description of the sub-status, e.g. follow_bank_transfer_instructions, follow_voucher_instructions or partially_funded. Descriptive only - not searchable.
"ch_1GVaEEFi2CnH4uN3ouw69fw3"Gateway’s transaction identifier
"pi_1GVaEEFi2CnH4uN355ZdZvk5 (TEST)"Authorization code from the gateway
"REF-00010000"Customer-facing reference
"100"Transaction amount
"GBP"Transaction currency
"2020-04-08T09:29:48.000Z"Creation timestamp
"2020-04-08T09:29:52.000Z"Last update timestamp
"2020-04-08T09:29:51.000Z"Processing timestamp
"2020-04-08T09:29:51.000Z"When the transaction was resolved
"2020-04-13T00:00:00.000Z"Intended payment date. Present only when the transaction was created ahead of its target date because the payment method requires gateway advance notice (e.g. SEPA/BACS/GoCardless/Stripe ACH). This is the target date, not the settlement date, and is omitted for payment methods that charge on the due date.
Payment identifier (legacy format - use payment.id instead)
Your supplied payment reference (legacy format - use payment.alt_key instead)
Payment description (legacy format - use payment.description instead)
Payment source (legacy format - use payment.source instead)
Payment action type (legacy format - use payment.action instead)
Payment status (legacy format - use payment.status instead)
Bad request - invalid parameters
Every error has a code and a message. Some add more fields alongside them, with detail about the error.
object
The error code, for example VALIDATION_ERROR, INVALID, INVALID_REQUEST, UNAUTHORIZED, FORBIDDEN or NOT_FOUND. Program against this, not the message.
What went wrong, in words, for logs and support.
Unauthorised: the API key is missing or not valid
Every error has a code and a message. Some add more fields alongside them, with detail about the error.
object
The error code, for example VALIDATION_ERROR, INVALID, INVALID_REQUEST, UNAUTHORIZED, FORBIDDEN or NOT_FOUND. Program against this, not the message.
What went wrong, in words, for logs and support.
Example
{ "code": "UNAUTHORIZED", "message": "Unauthorised"}Payment not found
Every error has a code and a message. Some add more fields alongside them, with detail about the error.
object
The error code, for example VALIDATION_ERROR, INVALID, INVALID_REQUEST, UNAUTHORIZED, FORBIDDEN or NOT_FOUND. Program against this, not the message.
What went wrong, in words, for logs and support.
Was this page helpful?
What went wrong?
Thanks for telling us.