Customer deposit
dep_3281 · USDC
25,000.00
=
Journal entry
journal_3281 · USDC
25,000.00
matched
For fintech
Bring blockchain state, pricing context and settlement evidence into one operational flow — before a balance reaches the customer ledger.
- RPC + DATA
- One integration surface
- 24 / 7
- Continuous operations
- CHAIN → FIAT
- Valuation context
- 1 : 1
- Event-to-entry trace
Settlement sandbox
batch · 2026-08-19T17:42Z
Chain event
stl_8f21a
25,000.00 USDC
- Network
- Ethereum
- Finality policy
- 18 / 12
- Reference price
- $1.00
Journal entry
jr_10482
Debit · settlement asset$25,002.50Credit · customer funds$25,002.50
- USD valuation
- $25,002.50
- Idempotency key
- stl_8f21a
The settlement rail
One event. Three proofs. One journal entry.
A transaction hash is not enough for a financial record. Preserve what happened on-chain, how it was valued and which policy allowed it into the ledger.
- 01
Observe the event
Read the transaction, receipt, block and canonical chain state from the network.
tx hash · block · status
- 02
Attach market context
Bind the asset amount to a timestamped reference price and a known quote source.
pair · price · observed at
- 03
Apply your policy
Check confirmation depth, freshness, allowlists and the rules for this product flow.
finality · limits · decision
- 04
Post exactly once
Create the journal entry with the event id as its replay-safe idempotency key.
journal id · proof hash
Proof bundle
The receipt travels with the money.
Support, finance and engineering inspect the same evidence instead of reconstructing a decision from three dashboards.
- tx_hash
- 0x8f21…91c4
- price_at
- 17:42:08Z
- policy
- 12_conf_v3
- result
- MATCHED
Reconciliation
Make chain and ledger close on the same line.
Compare external settlement with internal entries by identity, asset and amount. Exceptions stay visible instead of disappearing into a daily total.
- Sample batch
- #1048
- Matched
- 3 / 4
- Review
- 1
Treasury rebalance
trs_0914 · BTC
0.42000000
=
Journal entry
journal_0914 · BTC
0.42000000
matched
Customer payout
pay_7742 · ETH
8.750000
=
Journal entry
journal_7742 · ETH
8.750000
matched
Network fee
fee_1138 · ETH
0.003812
≠
Journal entry
journal_1138 · ETH
0.003790
review
Customer deposit
dep_3281 · USDC
- Chain evidence
- 25,000.00
- Internal ledger
- 25,000.00
Treasury rebalance
trs_0914 · BTC
- Chain evidence
- 0.42000000
- Internal ledger
- 0.42000000
Customer payout
pay_7742 · ETH
- Chain evidence
- 8.750000
- Internal ledger
- 8.750000
Network fee
fee_1138 · ETH
- Chain evidence
- 0.003812
- Internal ledger
- 0.003790
Policy before posting
Turn edge cases into explicit gates.
Financial workflows fail at the boundaries: stale prices, reorgs, retries and evidence gaps. Name each boundary before it becomes an incident.
eventpolicy gateentry
01
Price freshness
Reject a valuation when its market timestamp falls outside the product's allowed window.
if seen_at <= price_at + ttl
02
Network finality
Keep observed and credited states separate until the network-specific policy is satisfied.
if confirmations >= required
03
Replay safety
Retries may repeat delivery; they must never repeat the financial effect.
if event_id not in journal
04
Evidence integrity
Export the decision with the same proof hash used when the entry was created.
if proof_hash == export_hash
Shared or dedicated
The shared endpoint stays right there — it is the easy place to start and to test.
Both run on the same API and the same key, so you can keep part of the traffic on the shared pool and move only the critical part to your own node.
| Criterion | Shared RPC | Dedicated nodes |
|---|---|---|
| Capacity | Shared pool, scaled by us | Reserved node, yours alone |
| Noisy neighbours | Fair queue per key | None — single tenant |
| Rate limits | Per plan, burst-friendly | Whatever the node can serve |
| Archive | Included | Included, custom retention |
| Placement | Nearest healthy region | Pinned to your region |
| Setup | Instant | Provisioned within a day |
| Best for | Wallets, apps, bursty traffic | Exchanges, indexers, steady load |
Capacity
01- Shared RPC
- Shared pool, scaled by us
- Dedicated nodes
- Reserved node, yours alone
Noisy neighbours
02- Shared RPC
- Fair queue per key
- Dedicated nodes
- None — single tenant
Rate limits
03- Shared RPC
- Per plan, burst-friendly
- Dedicated nodes
- Whatever the node can serve
Archive
04- Shared RPC
- Included
- Dedicated nodes
- Included, custom retention
Placement
05- Shared RPC
- Nearest healthy region
- Dedicated nodes
- Pinned to your region
Setup
06- Shared RPC
- Instant
- Dedicated nodes
- Provisioned within a day
Best for
07- Shared RPC
- Wallets, apps, bursty traffic
- Dedicated nodes
- Exchanges, indexers, steady load
Questions
Before blockchain data reaches the ledger
Infrastructure shouldn't be the thing slowing you down.
Free to start. No credit card required.