← Stories
Treasury management
CFOs, shared-service centres, and finance ops — clear settlement events from open banking routing, and payment links when partners pay outside the ERP cycle.
Treasury cares about predictable cash-in and clean matching. StixBNK concentrates open banking routing collections (API checkout and merchant programmes) into status webhooks and stable references, while invoicing & payment links give counterparties a simple pay URL when a PO invoice sits outside your usual rails.
Use case 1
Reconcile routed A2A collections
Objective
Replace “which wire was this?” with machine-readable payment references from hosted checkout and API collections — posted into ERP on webhook confirmation.
Flow
- Merchant or API initiates a collection with a unique reference.
- StixBNK routes Pay by bank and returns status events.
- Finance matches amount + reference to open receivables.
- Exceptions queue only the residual mismatches.
Impact
↓ manualFewer remittance guesswork tickets
CloseEarlier visibility when A2A settles same-day
Use case 2
Partner invoices & payment links
When a supplier, affiliate, or subsidiary needs to pay you (or you need them to settle a balance), issue an invoice and share a hosted payment link. Settlement uses the same open banking routing as your gateway — one provider map, one ops playbook.
Flow
- Finance issues the invoice in StixBNK.
- Counterparty opens the pay link and completes bank SCA.
- Webhook + receipt confirm; cash application updates.
Impact
Self-servePartners pay without IBAN copy-paste errors
One stackInvoices and API collections share routing
