Issue stablecoins. Settle 24/7. Automate treasury and payment flows. RP1 gives banks one programmable rail without giving up control of reserves, policy, or customers.
Banks should not have to choose between the control of their existing stack and the speed of open networks.
RP1 connects bank policy to programmable settlement. The bank defines the money and the operating boundary. RP1 makes it move, reconcile, and compose.
Operating sequence01/ 04
01Reserve connection
02Controlled issuance
03Always-on settlement
04Reconciliation and redemption
Control boundaryReserves + identity
Current stageReserve connection
Reserve connection
Start with money the bank controls.
Connect reserve, custody, and identity systems without handing the operating model to a black box. RP1 becomes the programmable rail, not the owner of the relationship.
Pilot-defined integration boundary
Controlled issuance
Issue programmable money under bank policy.
Define the denomination, issuer roles, supply limits, transfer policy, and redemption path. Every mint and burn becomes an attributable onchain event.
Available for RP1 testnet pilots
Always-on settlement
Settle when customers need it.
Settle bank-issued value across RP1 without waiting for a batch window. Use native accounts and integration surfaces built for payment, treasury, and agent-driven workflows.
Sub-second finality measured on RP1 testnet
Reconciliation and redemption
Reconcile every movement. Redeem by design.
Query supply, settlement, and redemption events from one shared record. Feed those events back into treasury and ledger workflows instead of reconciling disconnected networks by hand.
Available through RP1 testnet query surfaces
Operating boundary
Control stays where the accountability lives.
RP1 does not replace the bank’s ledger, custody, or compliance stack. It gives those systems an execution and settlement layer they can program and verify.
LayerThe bank controlsRP1 providesPilot status
Reserve custodyBank and appointed custodiansReserve-linked issuance primitivesPilot-defined
Customer identityBank policy and compliance systemsPermission and role hooksPilot-defined
Issuance policyRoles, caps, pause and redemption rulesOnchain executionTestnet
SettlementApproved corridors and counterpartiesFinality and transaction stateTestnet
ReconciliationBank ledger and reporting workflowQueryable events and APIsTestnet
Testnet capabilities are available for pilot evaluation. Production scope, custody providers, compliance systems, and settlement corridors are agreed during diligence. Review RP1 documentation.
Define the control model, connect the required systems, and validate the complete issue-to-redeem lifecycle against RP1 testnet infrastructure. Production scope follows technical, security, compliance, and operational diligence.