The KibiPay blog

A single handle can now point at a phone, email, bank account, or Solana wallet. Here is how KibiPay's cross-rail directory turns one alias into a payable identity.

Paying by alias splits addressing from routing: resolve the handle, then let the engine choose Mojaloop for a phone, ACH for a bank, or Solana for a wallet.

Before a phone number becomes a payable alias, it should be proven. Here is how a reply-1 SMS double opt-in confirms ownership and satisfies A2P 10DLC consent.

Magic links let users prove they own an email and sign in without a password. Here is how single-use tokenized links work and why they are safe for payments onboarding.

A QR code can carry your alias and an amount so a payer scans, confirms, and sends. Here is how request-to-pay QR and scan-to-pay deep links actually work.

Sometimes the fastest way to get paid is a text message. SMS request-to-pay sends a tap-to-pay link that opens a pre-filled payment for the recipient.

A mock ACH rail models US bank payouts by ABA routing number and account so you can build and test bank transfers without touching real money.

US ABA routing, UK sort codes, MSISDNs, and base58 wallet strings all name a destination differently. Here is how each works and how a directory unifies them.

PIX keys, UPI VPAs, and Mojaloop's Account Lookup Service all solve the same problem. Here is how proxy addressing works and how a directory generalizes them.

A verified email is a great start, but an @handle is easier to share and remember. Here is how KibiPay turns registration into a payable directory identity.

Constraining each person to one alias per type prevents ambiguous routing and simplifies verification. Here is why that rule keeps a payment directory correct.

A browser-extension wallet keeps keys on your device while letting you pay any alias or scan a QR. Here is how self-custody meets cross-rail resolution.

Directory verification proves an alias is owned; confirmation of payee proves it is the person you meant. Here is how the two trust checks work together.

Sending money to a phone number over Mojaloop turns an MSISDN into a destination through lookup, quote, and transfer. Here is how the mobile-money flow works.

Smart routing turns rail selection into a scoring problem, weighing cost, speed, and reach to pick Mojaloop, ACH, FPS, or Solana for each individual payment.

A payment address book is more than saved contacts. Here is how to model aliases, verification, and privacy so users can pay saved people safely across rails.

For a payments demo, every second of signup friction costs testers. Magic-link accounts get people from email to payable identity in seconds, no passwords needed.

A real-time SMS receipt turns a payment into a moment of trust. Here is what belongs in a transactional receipt and how live confirmations keep users confident.

An unverified alias is a claim; a verified one is proof. Here is why KibiPay gates payability on verification and how each alias type earns verified status.

Trace a single payment from typing a handle to funds landing: directory lookup, name confirmation, smart routing, and settlement across whichever rail wins.

The eurozone runs its high-value settlement on TARGET2 and its instant retail payments on TIPS, both in central bank money. Here is how the Eurosystem's rails interlock.

Australia's New Payments Platform brought real-time, data-rich account-to-account payments, addressable by a simple PayID. Here is how NPP, Osko, and PayID fit together.

A single Arabic or Cyrillic name can be spelled a dozen ways in Latin script. That variability is why sanctions screening is fuzzy, noisy, and genuinely hard.

A company can be sanctioned without ever appearing on a list. OFAC's 50 percent rule extends blocking to entities owned by sanctioned parties — here is how it works.

One of the hardest laundering methods to detect hides dirty money inside legitimate-looking trade. Here are the core trade-based money laundering typologies and their red flags.

Behind every corporate customer is a real human who ultimately owns or controls it. Finding that person — the ultimate beneficial owner — is a core AML obligation.

Every payment that a human has to fix by hand is slower and costlier. Straight-through processing and message repair are the levers that decide which is which.

Long before XML and JSON, banks encoded payments as rows of fixed character positions. These formats are still everywhere — here is how they work and why they persist.

People say "ISO 20022" and mean XML, but the standard is really a logical model that can be serialized many ways. Separating model from syntax avoids costly confusion.

Request to pay lets a payee ask for money and the payer approve it. In ISO 20022 that conversation is carried by pain.013 and pain.014 — here is how the pair works.

The camt family carries account reporting in ISO 20022. Knowing when to use the end-of-day statement versus the transaction-level notification is key to clean reconciliation.

Paying a phone number instead of a sort code and account number depends on a proxy directory that resolves aliases to real accounts. Here is how that layer works.

The old way moves money through a chain of intermediary banks; the new way settles instantly on shared infrastructure. Understanding both explains modern cross-border payments.

Whether the payer or the payee starts a transaction changes everything downstream — authorization, risk, reversibility. Here is how push and pull payments really differ.

India's UPI ID, Australia's PayID, Brazil's Pix Key and Singapore's PayNow all replace account numbers with simple aliases. Here is how the four schemes compare.

Japan's Zengin network has cleared domestic bank transfers for decades on a fixed-length format. Its move to ISO 20022 is a major modernisation. Here is what changes.

Brazil's Pix reached hundreds of millions of users within a few years of its 2020 launch. Here is how its design choices made it a model for instant payment rails.

Sanctions compliance draws a sharp line between blocking a payment and rejecting it. Confusing the two can itself be a violation. Here is how to tell them apart.

UN sanctions bind member states through the Security Council; UK sanctions are set nationally and enforced by OFSI. Here is how the two regimes compare for compliance.

When money settles irrevocably in seconds, compliance has no overnight batch to fall back on. Here is how AML and sanctions screening work inside an instant-payment SLA.

When a firm suspects money laundering, it files a Suspicious Activity Report to the financial intelligence unit. Here is what triggers a SAR and how filing works.

Early fintechs read bank data by logging in as the customer and scraping the screen. Open banking APIs replaced that fragile, risky pattern. Here is the shift.

Long before XML and JSON, UN/EDIFACT structured business-to-business messages including payments. Here is how its compact segment syntax works and why it persists.

For decades payment data was clipped to fit cramped fields. ISO 20022 enriched data ends the truncation, carrying full party and remittance detail end to end.

Sanctions screening is only as good as the data it reads. ISO 20022 replaces cramped free-text fields with structured party data, cutting both misses and false hits.

The pacs.002 message is how a payment scheme tells you whether a payment was accepted or rejected. Here is what it carries and how status codes work.

Confirmation of Payee verifies that the name you typed matches the account you are paying, before the money leaves. Here is how the name-check actually works.

Central bank digital currencies promise a payment rail where the money is a direct claim on the central bank. Here is how retail and wholesale designs actually work.

Card networks and bank transfer schemes both move money, but they authorise, settle and dispute payments very differently. Here is how the two rails compare.

Mojaloop is open-source software that lets countries build interoperable instant payment switches connecting banks, mobile money, and fintechs — aimed at financial inclusion.

Canada's payments modernization pairs the widely used Interac e-Transfer with a new instant Real-Time Rail from Payments Canada. Here is how the two relate.

The United States runs two competing instant payment rails: the Fed's FedNow and The Clearing House's RTP. Here is how they compare on reach, limits, and design.

A sanctions screen is only as good as the list behind it. Keeping watchlists current — ingesting updates, versioning, and rescreening — is an operational discipline of its own.

The EU maintains a consolidated list of everyone subject to its financial sanctions. Here is what it contains, how it differs from OFAC lists, and how screening uses it.

An AML monitoring system is only as good as its tuning. Learn how thresholds are set, tested above and below the line, and governed as models that can go wrong.

Breaking a big deposit into many small ones to stay under reporting limits is one of the oldest laundering tricks. Here is how structuring works and how it is caught.

Old payment formats never seem to die. The reasons are less about technology and more about embedded infrastructure, certification cost, and the risk of moving money.

Nearly every card swipe, tap, and ATM withdrawal rides on a decades-old standard called ISO 8583. Here is how its bitmap-and-data-element format actually works.

Not every payment succeeds. ISO 20022 has a structured way to say no — from schema errors to business rejections — with status messages and standardised reason codes.

Every modern ISO 20022 payment travels with an envelope called the Business Application Header. It carries the who, what, and when that the message body leaves out.

Two ISO 20022 messages get confused constantly: pain.001 and pacs.008. One is how a customer tells its bank to pay; the other is how banks move money between themselves.

Before money can move, a payment needs an address. From sort codes to IBANs to phone-number aliases, here is how account identifiers actually route funds.

Instant rails move money in seconds, but the features people love — pay-by-phone-number, payment requests, name checks — live in a layer on top called overlay services.

Two settlement models sit under almost every payment rail: settle each transaction on its own, or net a batch and move the difference. The choice shapes risk and liquidity.

Instead of one global rail, cross-border instant payments increasingly bridge national instant systems. Here are the models, and how FX and settlement work.

FAST moves the money; PayNow lets you address it with a phone number or ID. Here is how Singapore's instant-payment stack fits together and links abroad.

SEPA Instant and UK Faster Payments both promise near-instant credit transfers, but their rules, limits, and reach differ. Here is a practical comparison.

Screening a payment means reading the right ISO 20022 fields. Here is where the parties and agents live in pain.001 and pacs.008, and why structure helps.

Sanctions screening is a fuzzy name-matching problem with high stakes. Here is how matching algorithms, transliteration, and score thresholds actually work.

The vast majority of AML screening alerts are false positives. Here is what drives them and the practical levers teams use to bring the noise down.

Rules fire on thresholds; typologies describe how laundering actually behaves. Here is how the two work together in AML transaction monitoring.

MT940 and MT942 are the workhorse SWIFT statement messages for corporate cash reporting. Here is what each carries and how their fields map to reconciliation.

For decades, cross-border banking ran on SWIFT's FIN network and its numbered MT messages. Here is how FIN works and how to read message-type numbers.

The move to ISO 20022 is a coordinated global migration with staggered deadlines. Here is how the cross-border and major domestic timelines fit together.

Purpose and category-purpose codes tell the payment chain why money is moving. Here is what each does, where they live in the message, and why they matter.

Most people meet ISO 20022 as XML messages, but its real power is the underlying model and shared dictionary. Here is the layered thinking behind the standard.

A payment submitted at 4:59pm and one at 5:01pm can settle a day apart. Here is how batch windows, cut-off times, and value dates actually work.

Request to Pay is a messaging layer that lets billers ask for payment while payers stay in control. Here is how it sits between direct debit and instant credit transfer.

RTGS systems settle each payment individually and irrevocably in central bank money. Here is how they work and why they underpin almost every other rail.

PromptPay lets Thais send money using just a phone number or national ID. Here is how the proxy-addressing system works and why it reshaped payments in Thailand.

SPEI is Mexico's central-bank-run instant payment system, settling interbank transfers in seconds. Here is how it works and how CLABE and CoDi fit in.

Faster Payments and India's UPI both move money instantly, yet their designs diverge sharply. Comparing them reveals two philosophies of instant payments.

Sanctions evasion is not random; it follows recognisable typologies. Here are the main patterns compliance teams watch for and the red flags that expose them.

The OFAC SDN list is the backbone of US sanctions enforcement in payments. Here is what it contains and how screening against it actually works.

The Travel Rule requires identifying information to travel alongside a transfer. Here is where it came from, how it works for wires, and why crypto makes it hard.

KYC, CDD, and EDD get used interchangeably but describe different layers of the same anti-money-laundering process. Here is how they actually relate.

Before SWIFT, cross-border payment instructions travelled by Telex, authenticated with manually calculated test keys. Here is how banks wired money in the pre-network era.

The US ACH network still moves trillions on a fixed-width file format defined by NACHA. Here is how that file is structured and why the details matter.

Representing money correctly is harder than it looks. Here is how ISO 20022 handles amounts, currencies, and decimal precision, and where naive rounding goes wrong.

The global migration from SWIFT MT messages to ISO 20022 MX is reshaping cross-border payments. Here is how the mapping works and where the hard problems hide.

A refund and a chargeback both return money, but they work in completely different ways. Here is how different rails handle reversals and disputes.

Instant payments look free to the sender, but real costs sit underneath: liquidity, fraud, and running settlement around the clock. Here is who actually pays.

What actually happens in the few seconds between hitting send and the money arriving? Here is a UK Faster Payment traced end to end, from message to settlement.

The New Payments Architecture is the long-running programme to retire the UK's Faster Payments and Bacs infrastructure. Here is what it actually changes and why it matters to builders.

Sweden's Swish turned instant mobile payments into a national habit and helped make the country nearly cashless. That success has triggered a serious debate about resilience and inclusion.

Nigeria's NIBSS Instant Payment settles account-to-account transfers in seconds and processes billions of transactions a year. It anchors a wider wave of African instant rails.

Sanctions screening is not just about names on a list. Comprehensive country programs and vessel screening — IMO numbers, AIS tracking, dark-fleet tactics — add whole other dimensions.

Primary sanctions bind those under a country's jurisdiction. Secondary sanctions reach further, threatening foreign firms with exclusion for dealing with sanctioned parties.

Reviewing customers on a fixed calendar leaves risk stale between cycles. Perpetual KYC replaces periodic refreshes with continuous, event-driven monitoring.

Rather than treating every customer identically, a risk-based approach concentrates AML effort where the danger is greatest. Here is how the FATF framework turns risk into controls.

Placement, layering, integration: the classic model of money laundering explains how illicit funds are disguised, and where controls have the best chance of catching them.

Fedwire has settled US dollar wires since the telegraph era. Its tag-based message format still shapes how high-value payments are described, even as ISO 20022 arrives.

Standard 18 is the fixed-width file format that has carried UK Bacs payments for decades. Here is how its label records, 100-character data lines and transaction codes fit together.

Who is paying whom, and through which banks? ISO 20022 answers with a rich, structured model of parties and agents, using identifiers like the LEI and BIC to remove ambiguity.

For decades payments carried a free-text memo field and little else. ISO 20022 structured remittance data changes that, letting invoices travel with the money and reconcile automatically.

Instant payment schemes must choose how obligations are backed: pre-funded balances that eliminate credit risk, or net credit positions that save liquidity. The trade-off shapes the whole rail.

Rails go down, time out, and return ambiguous results. Resilient payment systems plan for failure with failover routing, idempotency and disciplined reconciliation.

A payment is not done when it looks done on screen. Settlement finality is the legal moment money becomes irrevocable, and it is the concept that keeps payment systems safe.

Bacs Direct Debit is the UK's pull-based collection rail, running on a strict three-day clearing cycle. This walks through what happens from mandate to money movement.

China's payment plumbing splits into CNAPS for domestic settlement and CIPS for cross-border renminbi. Here is what each does and how they relate to SWIFT.

UPI made instant, interoperable, account-to-account payments a public utility in India. Here is how its architecture works and what makes it a global reference model.

A screening alert is only the start. Here is the operational playbook for investigating a hit, deciding to block or reject, freezing funds, and reporting to OFAC.

Sanctioned names arrive misspelled, transliterated and reordered, so exact matching fails. Here is how Levenshtein, Jaro-Winkler and phonetic algorithms close the gap.

The FATF Recommendations are the global backbone of AML and counter-terrorist financing. Here is how the 40 Recommendations are structured and enforced.

Politically exposed persons carry elevated corruption risk, so regulated firms apply enhanced scrutiny. Here is who counts as a PEP, and what screening actually requires.

AML is more than a sanctions screen. Here are the real pillars: customer due diligence, ongoing monitoring, suspicious activity reporting, and the risk-based approach.

BAI2 is the workhorse format for cash management and bank reporting in the US. Here is its record hierarchy, type codes, and how to read a file.

Before ISO 20022, cross-border payments spoke SWIFT MT. Here is how the block structure and numbered fields of MT103 and MT202 actually work.

Instant rails process ISO 20022 credit transfers in seconds, around the clock, at enormous volume. Here is how pacs.008 and pacs.002 work under real-time SLAs.

The UK's high-value rail moved from SWIFT MT messages to ISO 20022 in 2023, part of the Bank of England's RTGS renewal. Here is what changed and why the richer data matters.

A payment that leaves your account is not always the end of the story. Here is what returns, reversals, recalls and reject codes mean, and how money finds its way back.

Instant and gross settlement systems can only move money that is actually available. Here is how banks fund positions, and how netting and liquidity-saving mechanisms stretch scarce liquidity.

People say scheme, network and rail interchangeably, but a scheme is something specific: the rulebook, membership and governance that make interoperable payments possible.

The UK runs two very different interbank rails: near-instant Faster Payments and high-value CHAPS. Knowing when to use each comes down to limits, timing and settlement risk.

A payment can be authorized in a second but settled hours later. That gap is where liquidity and settlement risk live — here is how systems manage it.

Every reliable payment system rests on a centuries-old idea: record every movement of money twice so the books always balance.

Networks fail and clients retry. Here is how idempotency keys and careful retry design stop a single payment from being charged twice.

Mobile money turns a basic phone into an account. Here is how it works and why it became a cornerstone of financial inclusion.

Mojaloop is an open-source platform that lets separate financial providers connect to one shared switch so money moves between them in real time.

Sanctions screening checks parties and payments against restricted lists. Here are the basics: lists, matching, false positives, and where it fits.

APP fraud tricks people into authorising payments to criminals. Confirmation of Payee checks the name before you pay. Here is how it works.

Real-time monitoring evaluates payments as they happen. Here is how the pipeline works, from ingestion to decision, and why the timing matters.

Tazama is an open-source platform for real-time fraud and AML transaction monitoring. Here is how it is designed and where it fits.

Open-source tooling now covers much of the anti-fraud and AML stack. Here is how the categories fit together and where projects like Tazama sit.

Instant payments have gone from novelty to expectation across much of the world. A grounded look at where adoption stands and what still holds it back.

Dozens of countries now run instant payment rails. This tour compares the major systems and draws out the design patterns that recur across all of them.

SEPA Instant and UK Faster Payments both deliver real-time euro and sterling transfers, but their scope and governance differ sharply. A builder's comparison.

India's UPI and Brazil's Pix reached mass adoption faster than almost any payment system in history. Here is how the two compare and what builders can learn.

The United States now runs two competing instant payment rails. Here is how FedNow and RTP compare on governance, reach, and messaging for the teams building on them.

Cross-border payments need more than a shared format, they need shared rules for using it. That is what CBPR+ provides on top of ISO 20022.

Better payment data means better financial-crime controls. Here is how ISO 20022's structured fields sharpen sanctions screening and transaction monitoring.

A payment is more than an amount, it is a story about why money moved. Structured remittance data lets that story travel with the payment and be read by machines.

The shift from legacy MT messages to ISO 20022 MX is a multi-year global migration. Here is how coexistence works and how to migrate without losing data.

ISO 20022 is becoming the common language of payments worldwide. Here is what the standard actually is, how its message families fit together, and why it matters.

Cross-border payments remain slow and costly compared to domestic rails. Here's how SWIFT and correspondent banking work, and what's challenging them.

Pix, Brazil's central-bank instant payment system, achieved mass adoption remarkably fast. Here's the design behind its success and lessons for builders.

UPI turned India into the world's most active instant payments market. Here's the architecture behind it and why builders everywhere study its design.

Before FedNow, The Clearing House launched RTP, a privately operated instant payment rail. Here's how it works and how it compares to the Fed's system.

FedNow is the Federal Reserve's instant payment rail, settling account-to-account transfers in seconds, any hour of any day. Here's what builders need to know.

Confirmation of Payee checks a payee's name before you send. Here's how the name-matching works and why it matters against APP fraud.

SEPA harmonized euro payments across Europe. Here's how SEPA Credit Transfer, Direct Debit, and SEPA Instant work for builders.

CHAPS is the rail behind house purchases and large corporate transfers. Here's how same-day, high-value settlement actually works.

Bacs is the UK's batch rail behind payroll and Direct Debits. Here's how its three-day cycle works and why it still matters for builders.

Faster Payments is the rail behind most instant bank transfers in the UK. Here's how it actually moves money in seconds, and what builders need to know.

Cards and bank transfers feel similar to users but work in completely different ways. Here is how the two worlds differ and when each wins.

A payment that looks instant to you often is not settled between banks for hours. Here is the real difference between clearing and settlement.

Who initiates the money movement — the payer or the payee — changes everything about risk and reversibility. Here is push vs pull, made clear.

Instant rails move money in seconds; batch rails move it in bulk on a schedule. Here is how each works and when each is the right tool.

Every payment travels over a rail — the shared infrastructure that moves money between accounts. Here is what rails actually are and why the choice matters.