Either the contract you need is already on chain and your systems only have to reach it, or it is yours and CryptoRail deploys it and connects it. Both end the same way: your back office acts on chain and knows, reliably, what happened.
Each pilot has its page, its demo video and its evidence. The rest of this page explains the two ways in.
Pay and get paid in stablecoins from your back office, with limits and approvals.
Watch the demo →
Place idle treasury in a lending pool within the limits you set, and take it back.
Watch the demo →
State that a supplier passed a check, anyone can verify it, and you can withdraw it.
Watch the demo →
Issue, move and redeem a tokenised asset on a network shared with your partners.
Watch the demo →
Your customers redeem points from their own accounts, and you pay the fees.
Watch the demo →
Import the ABI of the contracts you need, give them a name in your registry, and call them from your ERP, treasury or customer systems like any other internal service, under your policies, approvals and keys.
Place treasury in lending pools, provide or withdraw liquidity, read positions and rates, within the limits your policy sets per protocol.
Subscribe to and redeem tokenised money market funds and bonds already issued on chain, from the systems that manage your treasury.
Pay suppliers, partners and group entities in existing stablecoins, straight from the systems that decide the payment.
Record and check on-chain attestations and identity registry entries: credentials, accreditations, revocations.
CryptoRail does not need to know a protocol to reach it: an ABI, even a partial one, is enough, and the same holds for price feeds, registries and marketplaces. Each call is its own transaction, so the steps of an operation are ordered, not atomic; the items marked on the roadmap close that gap.
Your ERP or payment engine decides a payout in stablecoins or tokenised money; CryptoRail carries it. Large amounts wait for the approvers your policy names, every payment is signed with your own keys, and a payment that fails says why and what to do, instead of leaving finance guessing whether to resend.
Your treasury places stablecoins in Aave, the largest lending market, and takes them back, with a key of its own. The key can only deposit into Aave and withdraw back to your treasury, within a daily cap; large deposits wait for a treasurer. Your systems read the position, the rate it earns and market prices from Chainlink with how fresh each one is.
State on chain that a supplier passed a check, until a date, with the attestation service that already runs on the network. Anyone verifies it without asking you; withdrawing it waits for a reviewer. Your key may make only this kind of statement, and only an internal identifier and a fingerprint of the evidence ever go on chain.
Build your contracts with the tools your developers already use. CryptoRail deploys them with the same controls as any other operation, registers them, and makes every function and every event available to your systems.
Issue and move your tokenised assets on a public network or a permissioned one shared with your partners.
Your contracts, your customers' own accounts, and no gas for them to buy.
Escrow, traceability, settlement between partners: rules you write once and every party can verify.
The same contract, the same calls and the same controls, first on a test network, then on the real one.
Your contracts are compiled where they are written, in your repository; CryptoRail takes the build, deploys it under your policies and approvals with your signer, and from then on every function is a call your systems can make by the contract's name.
flowchart TD
R[Your repository: Hardhat or Foundry build] --> D[CryptoRail deploys it: your policies, approvals and signer]
D --> N[Test network first, then the real one]
N --> G[Registered under its name]
G --> A[Every function through the API]
G --> E[Its events into your back office]A consortium runs its own permissioned network, often without gas fees. CryptoRail speaks it natively: issuance, transfers and redemptions go out from your issuer's identities, with keys in your HSM, approvals enforced where the rules demand them, and a record of who approved what.
Loyalty programmes, digital tickets, certificates, in-app assets: your customers hold their own accounts, and asking them to buy gas first is where they drop off. CryptoRail sponsors their operations within the budgets you set and tells you what each one cost.
Whether the contract is a protocol you reach or one you deployed, reconciliation fails on the edge cases: an event seen twice, an event from a block the network later discarded, a delivery lost while a system was down. CryptoRail delivers the contracts' events and the outcome of your own operations so that your ledger can apply each exactly once, and exports the full history when an auditor asks.
A pilot environment stood up in minutes with nothing installed on your side.