Product
Where open banking payments fit in a modern payment stack
Open banking payments are strongest when they complement card rails, orchestration, and account data rather than replace every payment method.
Read notePAYMENT NOTES
Payment infrastructure notes for regulated teams
Read concise field notes on PCI MPoC, SoftPOS, routing, open banking, and card programs, written for teams that have to ship and prove the operating model.
READING MAP
Start with the operating question
Every note is written to answer a specific launch question: what must be certified, what can be routed, which rail fits, and what the support team needs after go-live.
Certification scope
What banks, PSPs, and acquirers should verify before an MPoC or Tap to Phone launch.
Routing policy
How to move beyond static provider priority lists and make routing decisions from live signals.
Rail selection
Where open banking belongs beside card acceptance, account data, and reconciliation.
Program operations
What product, risk, finance, and support teams need around the transaction after authorization.
LATEST NOTES
Read the notes in release order
Latest first, deliberately short, and focused on the decisions regulated payment teams make before production rollout.
Engineering
Payment orchestration routing rules that actually improve approval rate
How payment teams can move beyond static provider priority lists and build routing rules around cost, approval rate, BIN, and failover.
Read noteIndustry
PCI MPoC and SoftPOS: what banks should verify before launch
A practical launch checklist for banks and acquirers evaluating PCI MPoC-certified SoftPOS and Tap to Phone programs.
Read note
HAVE A LAUNCH QUESTION?
Bring the use case behind the article
A Firisbe payment engineer can map the product surface, certification boundary, routing model, and first pilot plan in one technical session.