Get transaction status
Retrieve the current status of a credit, polled by Meridian until the transaction is terminal.
Authorizations
Assume OAuth 2.0 client credentials issued by the bank, presented as a bearer token. Meridian can adapt to the bank's preferred authentication scheme during onboarding.
Path Parameters
Meridian's unique transaction identifier, as sent in the credit instruction.
64Response
Current status of the credit.
Outcome of a validate, commit, or status call. One shape for all three.
Echo of Meridian's transaction identifier.
Transaction state machine:
RECEIVED— registered; nothing checked and nothing movedVALIDATED— the recipient account passed eligibility checksPROCESSING— money movement is underwayCOMPLETED— terminal; the funds reached the recipientFAILED— terminal; the credit will not be deliveredUNKNOWN— outcome not yet determinable, for example a timeout in your core system or an unreachable downstream rail; not terminal
Status moves only forward through that order, though skipping steps is fine, and terminal
statuses must never change once reported. UNKNOWN is exempt from the ordering and may be
followed by any status. Prefer it over guessing FAILED, since a terminal status can never
be walked back.
RECEIVED, VALIDATED, PROCESSING, COMPLETED, FAILED, UNKNOWN The bank's own reference for the transfer, if one exists. Meridian stores this for reconciliation and support. Include it on every response after commit.
64Machine-readable failure code. Required whenever status is FAILED. Use a stable,
documented set; Meridian maps these to customer-facing outcomes. Recommended baseline:
ACCOUNT_NOT_FOUNDACCOUNT_INACTIVENAME_MISMATCHLIMIT_EXCEEDEDINVALID_AMOUNTCOMPLIANCE_REJECTEDINSUFFICIENT_FUNDS(sponsored account)DUPLICATE_TRANSACTIONBANK_SYSTEM_ERROR
Human-readable detail for the failure. Not shown to customers verbatim.
500RFC 3339 timestamp when the credit reached a final status.