Payment controls for RTP Send and Receive
Payments on The Clearing House’s Real-Time Payments (RTP®) network are final in seconds. Coinbax runs your screening, balance, and prefunded position checks as evidence-based controls before the payment is sent.
Run by The Clearing House
Each participant prefunds its position in a joint account at the Federal Reserve Bank of New York, which The Clearing House administers.
Open 24/7/365
Payments clear at any hour, so your policy executes without a person in the loop.
Final in seconds
RTP payments are irrevocable once sent. A failing check holds the payment instead of letting it through.
ISO 20022 messages
Structured remittance data lands in the same audit trail as every control result.
Transactions
87,500.00 USD
Coinbax Controls
Verify
Beneficiary Watchlist ScreenNov 7, 10:19:37 AM
Beneficiary Account VerificationNov 7, 10:19:40 AM
Account Balance CheckNov 7, 10:19:41 AM
Fund
- Reaper (Auto-Refund Fail-Safe)Nov 7, 10:19:44 AM
Move to GLNov 7, 10:19:46 AM
Position Liquidity CheckNov 7, 10:19:47 AM
Confirm
RTP SendNov 7, 10:20:52 AM
Settle
Ledger ReconciliationNov 7, 10:21:25 AM
Push Transaction MetadataNov 7, 10:21:26 AM
- Status
- Completed
- Amount
- 87,500.00 USD
- Rail
- RTP
- Template
- RTP Send
- Created
- Nov 7, 10:19am
- Completed
- Nov 7, 10:21am
How an RTP payment moves through Coinbax's evidence-based controls
Payment request
Your customer sends a payment.
Verify beneficiary
Customer and beneficiary identity, through your identity provider.
Compliance controls
Fraud risk and OFAC screening, run in parallel.
Identity, fraud, and sanctions providers
The providers you already run. Your institution owns the OFAC policy.
Customer notified
Pending status and expected release time, through your channel.
Liquidity control
Prefunded RTP position checked against your liquidity floor.
RTP position
Prefunded, read from your payment hub.
Policy met?
Liquidity and OFAC checked again.
Friday, 4:45 p.m.
The position is short. The payment stays pending and your treasury team is alerted. Once funded, it is released automatically. If the hold window expires, operations is alerted and the funds go back to the customer’s account.
Hold in general ledger
Pending in your core. Rechecked until the position is funded.
Restore funding
If funds are short, treasury tops up the position.
Release
Every control has passed, so the payment goes to your payment hub.
Evidence record
Append-only and time-stamped, tied to your policy.
Payment hub
Sends the payment to RTP and returns the response.
Core
Coinbax pushes the status, and your core reconciles.
RTP network
Clears and settles in seconds. The network’s clock starts on submission.
See the evidence- Message ID
- RTP7F2A91…C4D03E
- Settled at
- 2026-11-07T15:20:52Z
- Vendor response › Msg ID
- RTPB3E604…91A7D2
- Vendor response › Tx sts
- ACSC
- Vendor response › Operation
- pacs.002.001.10 (FIToFIPmtStsRpt)
- Vendor response › Orgnl msg ID
- RTP7F2A91…C4D03E
- Vendor response › Accptnc dt tm
- 2026-11-07T15:20:52Z
- Vendor response › Orgnl msg nm ID
- pacs.008.001.08
- Vendor response › Orgnl end to end ID
- E2E-RTP-4B71C0D28E95
- Vendor response › Fctv intr bk sttlm dt
- 2026-11-07
- Acknowledgement status
- settled
- Coinbax execution
- Your policy and systems
- Customer or network
How an RTP payment executes
- 01
Verify the beneficiary and the balance
Watchlist and account screens run on the beneficiary, and the core confirms the customer can cover the payment.
- 02
Hold the funds and check the position
The amount moves into your general ledger hold account and Coinbax confirms your prefunded position can cover the send.
- 03
Send only when everything passed
Approvals and review windows clear, then the RTP credit transfer goes out. If anything failed, nothing is sent and the funds return to the customer.
- 04
Reconcile and record
The core posting is matched to the RTP confirmation, and every control result lands in one audit trail.
Questions
RTP settles against a prefunded position. Checking it first means a short position holds the payment for funding rather than producing a rejected send.
In your own general ledger hold account, on your books. Coinbax never takes possession of the funds; it executes your policy on when they move.
No. RTP payments are final once sent, which is why Coinbax runs every control, approval, and review window before the send.
Coinbax works with the core and fraud monitoring providers your institution already runs. That includes cores such as Jack Henry, FIS, Fiserv, CSI, and Corelation for balance, general ledger, and reconciliation, and screening and fraud monitoring from providers such as Socure, Sardine, Alloy, and Verafin. If you use another provider, we connect to it when you onboard.
No. One policy covers both. Only the liquidity check and send step change, so your team writes the rules once.
One policy, every payment rail
FedNow
Controls before an instant payment leaves.
Stablecoins
Wallet screening, issuer checks, and escrow on chain.