The Rail.
One API beside your core. Here is how a payment moves, and who controls it at every step.
Submit, screen, sign, settle, credit
Nothing moves before compliance clears, and nothing is credited before finality.
Who can move the money
Your institution keeps
- Its customers and their deposits
- Its status as financial institution of record, and its BSA program
- Control of the keys that move principal
BeVyne never
- Holds, pools, or converts funds
- Holds a key that can move principal
- Credits the far side before recorded finality
The gates, and why they fail closed
| Reference | Control | Standing |
|---|---|---|
| OFAC sanctions program | Every payment is screened before your institution signs; a match blocks the payment and reverses the reservation. | Verified in code |
| 31 CFR 1020.410(a); 1010.410(f) | Travel Rule recordkeeping at the $3,000 threshold, gathered before the payment moves. | Verified in code |
| GENIUS Act §4 | Settlement will run in a payment stablecoin from a permitted issuer, subject to statutory reserve requirements. | Statute, not yet in force |
| Modeled on Reg J · 12 CFR 210.31; Reg CC · 229.10(b) | The receiving side is credited only after settlement finality, recorded as evidence. | Design rule, pre-pilot |
| Design rule | Retries, timeouts, and mismatches stop movement until resolved. The ledger is double-entry and integer-only; a reconciliation break freezes outbound until it is cleared. | Verified in code |
Do we need a wallet and stablecoins already?
A wallet: one, and it's a decision, not a build.
Your institution needs a single operating wallet on the settlement network, its key held by your institution or a qualified custodian. BeVyne orchestrates around it and never controls it. Nothing to develop; the only operational question is who holds the key.
Stablecoins: funded at go-live, held by you.
You don't need any today. Going live begins by funding a working balance: dollars go to the asset's issuer, the stablecoin lands in your wallet, and it redeems back to dollars the same way. No exchange accounts, no trading desk. The balance sits on your books under your control, and sizing it to your payment volumes is part of onboarding.
A crypto team: no.
No nodes to run, no chain operations, no new core. Your side sees an API and signed webhooks; the wallet and the asset are the only new nouns, and both arrive through onboarding, not before it.
Ask us the hard version of these questions.
Thirty minutes, no deck required. Bring your BSA officer if you like.
Request a walkthrough