Eight deterministic, browser-based tools covering the full real-time payment operations lifecycle — from FedNow participation readiness and ISO 20022 cross-rail compatibility through RTP fraud velocity rule building, UK PSR APP fraud reimbursement, BCBS 248 intraday credit facility sizing, and AP2 agentic policy compilation. FedNow · RTP · SEPA Instant · Faster Payments · PIX · PayNow. Zero PII.
Follow the 5-stage workflow below from participation readiness to agentic policy, or jump directly to any tool. All tools run in your browser — no account, no data transmission.
Score your institution's readiness against all 47 FedNow technical and operational participation requirements across 6 domains.
Identify exactly which fields behave differently between your source and target rails before cross-rail deployment.
Configure and validate fraud velocity rules within the sub-second RTP authorisation window (250ms–1,000ms latency budget).
Size your FedNow/RTP intraday credit facility under BCBS 248 and generate step-by-step PSR APP fraud claim workflows.
Compile your real-time payment operating policy across five dimensions into a validated Policy Mandate JSON for agentic consumption.
Score your institution's readiness against all 47 FedNow technical and operational participation requirements across 6 domains: Core Banking Connectivity, ISO 20022 Message Formats, Fraud Monitoring, Liquidity Management, Dispute & Return Handling, and Operational SLA & Governance. Outputs readiness score, priority gap checklist, implementation roadmap, and participation Policy Mandate JSON.
Open ToolCheck ISO 20022 message compatibility across real-time payment rail implementations. Select source and target rails (FedNow, RTP/TCH, SEPA Instant, Faster Payments, PIX, PayNow) and message type (pacs.008, pacs.002, pacs.004, camt.056). Returns a field-by-field compatibility matrix highlighting scheme overlay requirements, absent fields, and partial support — plus a severity-ranked diff report and Policy Mandate JSON message routing policy.
Open ToolConfigure and validate fraud velocity rules within the sub-second RTP authorisation window (250ms–1,000ms latency budget). Covers mule account detection, reverse-push/refund patterns, velocity thresholds for FedNow/RTP/PIX/Faster Payments, and rule conflict detection. Generates structured rule pseudocode, latency budget waterfall analysis, and Policy Mandate JSON RTP fraud policy.
Open ToolStep-by-step claim assessment workflow for UK PSR mandatory APP fraud reimbursement (October 2024 — PS24/3). Covers £85,000 cap calculation, gross negligence checklist (6 evidenced indicators), 50/50 sending/receiving PSP liability split, 5-business-day settlement clock, consumer vulnerability handling, and dispute escalation to FOS. Outputs operational decision playbook, dated milestone timeline, and Policy Mandate JSON claims handling mandate.
Open ToolModel intraday credit facility requirements under the Basel III LCR framework. Calculate the minimum intraday liquidity buffer, recommended facility size with 20% operational headroom, LCR ratio impact of pre-positioned collateral (with Basel III haircut by collateral type), and the full BCBS 248 ILM1–ILM7 indicator set. Peak debit stress scenarios at 1.5×, 2×, and 3×.
Open ToolCompile your real-time payment operating policy across five dimensions — rail eligibility, fraud velocity thresholds, liquidity buffer triggers, settlement window preferences, and escalation conditions — into a validated Policy Mandate JSON for agentic payment system consumption. Built-in policy validation catches threshold conflicts, band ordering errors, and unreachable rules. Generates a live JSON preview with syntax highlighting, agent instruction set, Markdown export, and one-click clipboard copy.
Open ToolGenerate a settlement failure recovery playbook for real-time payment rails. Input rail, failure type (liquidity / technical / sanctions hold), and customer type to receive a step-by-step recovery workflow, customer notification templates, and a regulatory reporting checklist.
Coming soon — pending demand signalSide-by-side comparison of scheme rules across FedNow, RTP/TCH, SEPA Instant, Faster Payments, and PIX. Covers transaction limits, credit-push enforcement, recall/return windows, dispute resolution timelines, and membership requirements.
Coming soon — pending demand signalLast reviewed: May 2026 · 6 active tools · Cat-21 · Real-Time Payments
Use T254 to identify field mapping issues before cross-rail go-live. Use T255 to scope your FedNow implementation against all 47 technical requirements. Use T256 to configure sub-second fraud rules within your latency budget.
Use T257 to generate step-by-step PSR APP fraud claim workflows for front-line ops teams. Export the Policy Mandate JSON as your compliance audit trail. Cross-link to Tool 26 for strategic portfolio-level liability modelling.
Use T258 to size your FedNow/RTP intraday credit facility under BCBS 248. The ILM1–ILM7 indicator set feeds your Pillar 2 supervisory reports. Cross-link to Tool 39 for the minute-by-minute prefunding picture.
Use T256 to design velocity rules within the 250ms–1,000ms authorisation window. The latency waterfall shows exactly how much of your budget each rule consumes. Conflict detection catches redundant BLOCK rules before deployment.
Use T259 to compile a Policy Mandate JSON your autonomous payment agent can consume via the AINumbers.co MCP server. The mandate covers all five operational dimensions with built-in validation — deployable directly into your agent runtime.
Use T255 to build a FedNow participation roadmap with stakeholders. The gap checklist turns into a project backlog. Use T254 to understand cross-rail field compatibility before committing to a multi-rail product strategy.
Start with T255 — FedNow Participation Readiness Scorer to score your institution against all 47 Federal Reserve requirements. The gap checklist becomes your implementation backlog. Then run T258 to size the intraday credit facility your FedNow volume will require under BCBS 248.
Use T254 — ISO 20022 Cross-Rail Compatibility Checker to identify exactly which fields behave differently between your source and target rails. The severity-ranked diff report shows HIGH/MEDIUM/LOW issues — prioritise HIGH before deployment.
Open T256 — RTP Fraud Velocity Rule Builder and select your rail and latency budget (start with 500ms). Add velocity rules one by one — the latency waterfall updates live. The conflict detection catches duplicate BLOCK rules and unreachable MONITOR conditions before you push to production.
Open T257 — PSR APP Fraud Reimbursement Workflow Builder and complete the 4-step claim assessment. The decision engine applies the £85,000 cap, calculates the 50/50 PSP split, assesses gross negligence across 6 evidenced indicators, and generates a dated 5-business-day timeline.
Open T258 — Intraday Credit Facility Sizing Model and enter your peak net debit position, average daily volume, and current LCR position. Select your collateral type — the haircut auto-populates from the Basel III table. The output shows your minimum buffer, recommended facility (buffer + 20% headroom), LCR impact, and all seven BCBS 248 ILM indicators.
Use T259 — AP2 Real-Time Payments Policy Builder to configure all five policy dimensions. The live JSON preview updates as you configure each section. The built-in validator catches threshold conflicts before you export. Download the Policy Mandate JSON and reference the agent_instructions array as your agent's ordered rulebook.
All 6 tools expose structured outputs compatible with the AINumbers MCP manifest. Use the tool IDs below with any MCP-capable agent.
| Tool ID | MCP Name | Input Schema | Output |
|---|---|---|---|
| T254 | check_iso20022_cross_rail_compatibility | source_rail, target_rail, message_type | compatibility_matrix{}, severity_diff[], policy_mandate_json |
| T255 | score_fednow_participation_readiness | institution_type, domains[], current_capabilities{} | readiness_score, gap_checklist[], roadmap{}, policy_mandate_json |
| T256 | build_rtp_fraud_velocity_rules | rail, latency_budget_ms, rules[] | rule_pseudocode{}, latency_waterfall{}, conflicts[], policy_mandate_json |
| T257 | build_psr_reimbursement_workflow | claim_amount, psp_role, gross_negligence_indicators[] | decision_playbook{}, timeline{}, psp_liability_split, policy_mandate_json |
| T258 | calculate_intraday_credit_facility | peak_net_debit, avg_daily_volume, lcr_position, collateral_type | min_buffer, recommended_facility, lcr_impact, ilm_indicators{} |
| T259 | build_ap2_rtp_policy | rail_eligibility{}, fraud_thresholds{}, liquidity_triggers{}, settlement_prefs{}, escalation{} | policy_mandate_json, agent_instructions[], validation_report{} |