The table below details the expected payment attributes and corresponding transaction object attributes that are used for matching purposes.
|Expected Payment Attribute
|The direction money is flowing in the expected transaction. Either credit or debit.
|The ID of one of your organization's Internal Accounts where you expect to receive the payment.
|The highest amount that the expected payment may be equal to. It is an inclusive bound.
|The lowest amount that the expected payment may be equal to. It is an inclusive bound.
|The expected payment type.
Supported types: ACH, BECS, Bacs, Book Transfer, Card, Cross Border, Check, EFT, Interac, ProvXchange, RTP, SEN, SEPA, Signet, Wire.
|The counterparty, or entity (a person or business), that you expect to receive money from.
Note: A counterparty must have a linked bank account in order for it to be used for matching.
Varies by payment
|The expected currency of the payment. Must conform to ISO 4217.
|The latest date that you expect the payment may arrive.
|The earliest date that you expect the payment may arrive.
|The statement description that you expect to see on the transaction.
For ACH: full line items passed from the bank
For Wire: the OBI field on the wire.
For Checks: the memo field.
Varies by payment
statement_descriptor fields are unique in how they are used for matching:
Counterparty: we retrieve the counterparty’s bank account details such as account name, account number, and routing number. Depending on the payment type, we perform “fuzzy” matching or “contains” matching against originator and beneficiary names found in the transaction and its metadata. Routing numbers use an exact match against the sender or receiver routing number.
Statement descriptor: depending on the payment type, we perform a “contains” match of the information specified in the Expected Payment against the full line items, OBI field, or memo field of a transaction and its metadata.
Updated 15 days ago