You only pay Attestyx for the validation service.
We never deduct our fee from your customers payments. Two unrelated money flows.
Cryptographically tied. Physically separated.
When we validate a payment, two transactions happen in parallel:
- Your customer's payment to their recipient. Moves on your existing rails. Your bank, your rail, your custody. We sign the authorization (Mode A) or attest after the fact (Mode B). We never see the funds.
- Your fee to Attestyx for the validation.Moves through your funding model: USDC prepaid balance, USD prepaid balance, postpaid invoice, or card-on-file. We bill you. We receive the fee.
Tying these two flows together cryptographically (via the validation_id) is what makes the audit trail work. Tying them together physically (deducting the fee out of the payment) would make us a money transmitter and break the entire compliance posture. We do the first. We never do the second.
| Model | When to use it | Settlement currency | Lead time |
|---|---|---|---|
| USDC prepaid | Crypto-native customers, high-frequency calls, treasury teams holding stablecoins | USDC | Minutes after network confirmation |
| USD prepaid (wire / ACH) | Most fintechs, marketplaces, banks | USD | Same day for wire, 1-2 business days for ACH |
| Postpaid invoice | Established customers with AP processes | USD or USDC | Net-15 or net-30 |
| Card-on-file fallback | Backup only | USD via Stripe | Real-time |
Send USDC to your customer-segregated balance.
The default chain is the JIL network for lowest latency and lowest gas. We also accept USDC on Ethereum, Base, and Solana via bridge. Funds are held in a smart contract scoped to your tenant. You can withdraw the full remaining balance at any time.
How it works
- Call
POST /v1/funding. Receive a contract address and memo. - Send USDC. Network confirms.
- Balance reflected in your portal within minutes.
- Auto-reload threshold optional.
- We debit the fee per Tier 1 call from your balance, in real-time.
- Withdraw anytime via
POST /v1/balance/withdraw.
Wire or ACH USD to your customer-segregated FBO account.
We hold the funds. You withdraw on demand.
Why FBO and not a general operating account: holding customer funds in a customer-segregated For Benefit Of account at a licensed bank, with funds bankruptcy-remote from us, is the standard prepaid-balance structure that does not trigger money-transmitter licensing. Your balance is yours. We are the operator of record on the validation service that draws against it.
Minimum initial funding:$500. Auto-reload optional. Withdrawal: ACH or wire.
Available after KYB plus 30 days of clean prepaid activity.
Net-15 or net-30. Settle by ACH, wire, or USDC.
The trade-off versus prepaid is a credit decision on our side: you have a credit limit, and high-volume customers may need to top up via prepaid above their limit.
Optional, configurable per tenant. Stripe-managed.
Purpose: prevent hard API failures when your primary funding source is unexpectedly depleted. If your prepaid balance hits zero and your postpaid limit is exhausted, we can either reject the API call with a billing failure, or fire the card on file to top up the prepaid balance and continue. Default is the latter when a card is on file.
This is a backup. It should not be your primary funding rail.
- We do not deduct our fee from your customer's payment to their recipient. Ever.
- We do not hold your customer's payment. Ever.
- We do not custody crypto in a non-segregated wallet.
- We do not custody fiat in a general operating account.
- We do not route or transmit your customer's payments through any of our infrastructure.
- USD banking partner:Modern Treasury / Column / Increase / Mercury - to be confirmed
- USDC chains supported at launch: JIL network (default), Ethereum, Base, Solana
- Card processor for fallback:Stripe
- Metering and billing engine:Metronome / Orb - to be confirmed