Get a transaction
GEThttps://app.shuttleglobal.com/c/api/instances/{instance_key}/transactions/{transaction_id}
Get details of a specific transaction.
You can expand the following fields:
account, captures, contract, created_session, gateway, parts, payment_method, refunds, source_transaction, updated_session
Authorizations
Section titled “Authorizations”Parameters
Section titled “Parameters”Path Parameters
Section titled “Path Parameters”The transaction’s ID (tr_...), or its alt_key.
Query Parameters
Section titled “Query Parameters”Fields to expand into full objects
Responses
Section titled “Responses”Successful response
object
object
The person the transaction was for
The type of transaction
Your reference for the transaction
The amount of the transaction
The authorisation code returned from the gateway
The amount authorised (and uncaptured) if an AUTH
The payment amount less any refunds
The browser’s IP address
The browser’s accept header
If the browser has javascript enabled
The browser’s locale
The browser’s user agent
The browser’s screen dimension
If the browser has java enabled
The browser’s color depth
The browser’s timezone
The IDs of any related captures
The amount of the authorisation that has been captured if an AUTH
(enterprise) The channel the transaction was processed via
The contract this transaction belongs to
When the transaction was created
The session the object was created by
The currency in ISO format
The order description
(enterprise) The designation the transaction was processed via
(enterprise) The division from which the payment was instructed
If action = AUTH the date the authorisation expires (where known)
The gateway the transaction was processed via
The status message returned by the gateway
Any metadata returned by the gateway
object
The gateway identifier for the transaction
The category or error message received from the gateway
For gateways that support it, a link to the processor’s dashboard
The ID of the transaction
When the transaction was instructed by the user
(enterprise) The initiative the transaction was for
(enterprise) The legal entity the transaction was processed via
The next payment attempt if a declined payment that was retried
Custom key-value pairs stored on the transaction
object
Array of parts objects for which charge(s) the transaction was applied to
The payment_method / card used
Whether a saved payment method token was used (true) or if payment details were submitted directly with this transaction (false)
When the transaction was processed
The URL if 3DS is required
If action == REFUND the reason for refund
The transaction customer facing reference (format BOLT-123445)
The IDs of any related refunds
If action == REFUND a link to the refund object
The amount of the transaction that has been refunded
When the transaction was resolved
The currency the transaction was settled in if different
The amount of fees deducted for processing
The amount paid in the settlement currency
The amount settled less fees
The source for the transaction
For refunds, references the transaction being refunded
The status of the transaction:
- SUCCESS - The transaction was approved
- PENDING - The transaction is still in progress
- DECLINED - The transaction 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
Sub-status of the transaction, present when the gateway is waiting for someone to act:
- CUSTOMER_ACTION_REQUIRED - the customer still has something to do, e.g. a bank transfer or Multibanco payment is PENDING until they make the transfer or pay the voucher
- MERCHANT_ACTION_REQUIRED - reserved for future use
- NO_ACTION_REQUIRED - nothing is outstanding
Omitted and NO_ACTION_REQUIRED mean the same thing - treat an absent sub_status as
no action required.
"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.
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.
When the transaction was last updated
The session the object was updated by
The amount of the authorisation that has been voided if an AUTH
The IDs of any related void transactions
The version of the object
Any workflows that were applied to the payment
The current status of the workflow
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.
Unauthorized - invalid credentials
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"}Transaction 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.