Login
Topic

Reference

6 posts

A blueprint schematic of five payment rails drawn as parallel mint lines labelled ACH, SEPA, Faster Payments, wire and push to card, each carrying a violet return marker with its failure code, and a dimension line noting that failure notice takes minutes to days.
Reference

Why payouts fail, by rail: a reference

ACH return codes, SEPA reason codes, wire rejections and push-to-card declines — what each means, which are retryable, and how long you wait to find out.

By Valeria VahorovskaRead more →A blueprint schematic in mint line-work on deep violet: a provider box sending a stream of webhook envelopes to a consumer box, one refund envelope lifted above the line and annotated as arriving late, with a dimension line reading event stream, eight classes.
Reference

Payment webhook events: a reference

What each event class means, why ordering is never guaranteed, and the five properties any webhook consumer needs before it can be trusted with money.

By Valeria VahorovskaRead more →A blueprint schematic of an invoice in mint line-work with three highlighted fields, payment reference, purchase order number and amount with currency, each leadered to a violet annotation reading critical, the logo box dashed and marked as having no match value, and a dimension line reading invoice, twelve fields.
Reference

The invoice fields that decide whether matching works

Twelve fields on an invoice, ranked by what they do for automated matching — which ones carry the link, which ones break it, and what to fix on your own template.

By Valeria VahorovskaRead more →A blueprint schematic of seven stacked rule boxes narrowing like a funnel, numbered identifier, exact, tolerance, one-to-many, many-to-one, fuzzy and rule-based, each marked with a confidence dot, the fuzzy row dashed in violet as suggest-only, and an exceptions outlet at the bottom.
Reference

Reconciliation matching rules: a reference

The seven rule types every matching engine uses, what each one catches, what it silently gets wrong, and the order to apply them in.

By Valeria VahorovskaRead more →
Reference

Bank statement formats: BAI2, MT940, CAMT.053, OFX and CSV

A reference for the file formats banks deliver transaction data in, what each one carries, what it loses, and which to ask for when reconciliation depends on it.

By Valeria VahorovskaRead more →
Reference

Payment decline codes: a reference

What each decline code means, whether retrying will ever work, and what to do instead. The ISO 8583 response codes most processors map onto, in one table.

By Valeria VahorovskaRead more →
Book a demo