Authorizations
Bearer authentication header of the form Bearer <token>
, where <token>
is your auth token.
Path Parameters
Transaction ID
"472341e0-ea3e-41a1-96bc-fd0185e1eac8"
Response
Posted Transaction
The creation date of the transaction
The "effective date" of a transaction. This may be earlier than posted_date in some cases (for example, a transaction that occurs on a Saturday may not be posted until the following Monday, but would have an effective date of Saturday)
The idempotency key used when initially creating this transaction.
"7d943c51-e4ff-4e57-9558-08cab6b963c7"
Whether or not this transaction represents a purely informational operation or an actual money movement
Whether or not this transaction was created operating in "lead ledger" mode
The date the transaction was posted. This is the date any money is considered to be added or removed from an account.
An external ID provided by the payment network to represent this transaction. This will always be null for internal transfers.
The specific transaction type. For example, for ach
, this may be "outgoing_debit".
The id of the tenant containing the resource. This is relevant for Fintechs that have multiple workspaces.
"abcdef_ghijkl"
The time the transaction occurred.
The general type of transaction. For example, "card" or "ach".
The date the transaction was last updated
The unique identifier of the transaction.
The set of disputes related to this transaction. Since a dispute can be for a partial amount of a transaction, a single transaction can be involved in multiple disputes.
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.