PAYMENT REQUESTS ↗
0Synthetic invoices generatedCYBER AGENCY/ R&D / OPENPAYGENTS
OPEN INFRASTRUCTURE / EXPERIMENT 001
Payments move.
Proof stays.
A merchant-controlled layer for verifying bank transfers, matching invoices, and keeping the record. No funds pass through OpenPaygents.
Three domestic networks modeled / One reconciliation interface
PAYMENT EVENT FLOW 01 / 03
ORDER01
BANK02
PROOF03
CHECK ACCOUNT · REFERENCE · AMOUNT · CURRENCY
SIMULATION ONLYSynthetic banks, synthetic transactions, and non-scannable QR artwork. No real transfers, banking credentials, or payments.
🇻🇳 VietQR SIMULATED
🇹🇭 PromptPay SIMULATED
🇧🇷 Pix SIMULATED
SIMULATED VERIFIED ↗
0Exact, independent matchesNEEDS REVIEW ↗
0Held from automatic fulfillmentUNIQUE ALLOCATIONS ↗
0Each receipt matched at most once01 / MERCHANT
Create a payment request
PAYMENT INSTRUCTIONAWAITING SELECTION
CURRENT REQUESTChoose or create an invoice
Bank instructions appear here when a synthetic request is selected.
Visual placeholder, not a functional bank QR code.
02 / BANK ADAPTER
Inject a bank event
Choose an invoice, then emulate what the merchant's bank might report. Exact receipts settle. Incorrect or unverified receipts are held for review.
●
LAST RESULTReady to simulate
Select a scenario to see the reconciliation decision.
01 Verify evidence source PENDING
02 Match invoice fields PENDING
03 Commit one allocation PENDING
04 Emit merchant event PENDING
03 / RECONCILIATION
Merchant ledger
| REFERENCE | NETWORK | DESCRIPTION | AMOUNT | STATUS |
|---|
All records are generated inside this browser
04 / AUDIT
Event history
05 / EXCEPTIONS
Held for review
UNDER THE HOOD
One interface.
Different bank networks.
OpenPaygents explores an account-to-account payment layer merchants can inspect, adapt, and operate themselves. The software verifies incoming records, reconciles orders, and makes exceptions visible. It does not operate a bank, custody funds, or promise universally free banking.
Try the payment laboratory ↗Source publication planned