Off-ramp and bill pay (crypto to fiat)
These are real limits, not samples:
The daily limit is shared across all of a user’s payouts — bank off-ramps and bill
payments draw from the same $150,000/day, not a separate allowance each. Read the live
values per account:
dailyRemaining reflects what’s left today and is shared across the user’s accounts, so
read it fresh before a payout rather than deriving it from dailyLimit yourself.
On-ramp (fiat to crypto)
The two on-ramp paths have different limit models.Auto-ramp accounts — wire and ACH push
Funds pushed into an auto-ramp account over wire, ACH push, FedNow, or SEPA have no upper limit — large transactions are welcome. There is no per-transaction or daily cap on what a user (or their employer or customer) sends in. Each supported pair carries a minimum, which you read — rather than hardcode — from the supported pairs list:minAmount. See the
on-ramp guide for the full
request and Settlement timing for how quickly each rail clears.
Linked bank on-ramp — ACH debit
Limits for linked bank on-ramps (ACH debit) are specific to the individual user and their account, so there’s no single published figure. Read them live before every deposit:minAmountUsd and maxAmountUsd the response
returns, keep the user on the amount screen if they exceed it, and re-read after a
blocked attempt. Never hardcode a value or try to infer the policy that produced it.
Raising limits
Limits can be lifted on demand. If a user needs higher off-ramp throughput or larger ACH-debit on-ramps than the defaults allow, Spritz runs standard enhanced due diligence (EDD) and raises the applicable limits for that user or your integration. Reach out to your Spritz contact to start the review.Related
Off-ramp: crypto to bank
Crypto in, fiat out — where the payout limits apply.
On-ramp: fiat to crypto
Auto-ramp accounts for wire and ACH push funding.
Linked bank on-ramp
ACH debit, with per-user deposit limits read live.
Amounts and currencies
How Spritz represents money in every request.