Authorizations
Bearer authentication header of the form Bearer <token>
, where <token>
is your auth token.
Path Parameters
Transaction ID
"472341e0-ea3e-41a1-96bc-fd0185e1eac8"
Query Parameters
Include a transaction for each clearing of an authorization.
Response
Transaction
Transaction metadata specific to transactions with type CARD
The set of valid CARD transaction subtypes
ATM_WITHDRAWAL
, ATM_WITHDRAWAL_REVERSAL
, BALANCE_INQUIRY
, CARD_NETWORK_FINAL_CHARGEBACK
, CARD_NETWORK_FINAL_CHARGEBACK_REVERSAL
, CARD_NETWORK_FIRST_CHARGEBACK
, CARD_NETWORK_FIRST_CHARGEBACK_REVERSAL
, CARD_NETWORK_REPRESENTMENT
, CARD_NETWORK_REPRESENTMENT_REVERSAL
, CARD_TRANSACTION
, CARD_TRANSACTION_REVERSAL
, CHARGEBACK
, CHARGEBACK_REVERSAL
, CREDIT
, CREDIT_REVERSAL
, DIRECTPOST
, DIRECTPOST_REVERSAL
, POS_CASHBACK
, POS_CASHBACK_REVERSAL
, POS_PURCHASE
, POS_PURCHASE_REFUND
, POS_PURCHASE_REFUND_REVERSAL
, POS_PURCHASE_REVERSAL
, POS_REFUND
, POS_REFUND_REVERSAL
, PROVISIONAL_CREDIT
, PROVISIONAL_CREDIT_REVERSAL
The total amount of the transaction including both pending and already posted amounts. The value is represented as the smallest denomination of the applicable currency.
The exact time the transaction was recorded in the ledger
ISO 4217 alphabetic currency code of the transfer amount
The dc_sign
represents the direction money was moved. A value of DEBIT
is money moving out of an account, a value of CREDIT
is money moving into an account
CREDIT
, DEBIT
The effective date of the transaction. This usually aligns with network settlement date, which differs between transaction types. The effective date is also used to determine effective daily balances for the purposes of interest calculation.
Determines whether or not a transaction or auth was "forced" or not. A forced transaction skips any account balance checks
The group id of the transaction. Every transaction in the ledger is one entry in a double-entry system and the primary and offset transactions share the same group_id
The unique identifier of the transaction
The date and time the transaction was last modified
Determines whether or not the funds on hold were the result of a partial auth or not. If true
the pending_amount
of the transaction will be less than the requested amount.
This is primarily used for certain types of card transactions.
The amount amount of the transaction currently authorized or on hold
The amount of the transaction that has been fully posted to the account
The status of the transaction
COMPLETE
, DECLINED
, PENDING
The time the transaction occurred. In most cases this will be roughly identical to creation_time, but it can differ in some situations if the payment doesn't appear in the ledger in real-time.
The type of the transaction. This typically represents the "payment" rail that is used. For example, for ACH payments this will be ach
, while debit card transactions will use card
.
ACH
, CARD
, CASH
, CHECK
, EXTERNAL_CARD
, FEDNOW
, FEE
, INTERNAL_TRANSFER
, REWARD
, SYNCTERA_PAY
, WIRE
The account uuid associated with the transaction. account_id
and internal_account_id
are mutually exclusive
"7d943c51-e4ff-4e57-9558-08cab6b963c7"
The uuid of the customer that initiated the transaction (if any)
The decline object provides information explaining why a declined transaction was declined.
A human-friendly description of the transaction, provided by the integrator
Enriched transaction metadata
Transaction fraud risk evaluation result
The date and time any pending amount is expected to be released back to the account.
The internal account uuid associated with the transaction. account_id
and internal_account_id
are mutually exclusive
"7d943c51-e4ff-4e57-9558-08cab6b963c7"
an unstructured json blob representing additional transaction information supplied by the integrator.
The date the transaction was posted (based on the bank calendar and end-of-day). For transaction with multiple postings, this is the date of the earliest posting.
This will be omitted for transactions with a posted_amount
of 0
.
An external ID provided by the payment network to represent this transaction. This is not guaranteed to be globally unique. This will always be omitted for internal transfers.
The date the transaction was settled according to Synctera's platform. Generally, this can be interpretted the date the transaction was actually processed and settlement by the payment network.
A human-friendly description of the transaction, provided by the Synctera platform