Skip to main content
POST
Prepare a direct deposit authorization

Authorizations

Authorization
string
header
required

User bearer credential: either a Cognito JWT or an ak_ user API key. Backend integrators using HMAC must include the user API key alongside the three HMAC headers on user-scoped endpoints.

Body

sourceId
string
required

Opaque public funding source identifier

Example:

"fs_01JV7Q8M4Y8K6N2Z5P3R1T9W0X"

address
string
required

Destination wallet address to deposit into. Validated but not proven via wallet signature; authorization is derived from the verified ACH funding source.

Example:

"9n4nbM75f5Ui33ZbPYXn59EwSb9Y1zdyu3x2b1f8jQRY"

network
enum<string>
required
Available options:
solana,
ethereum,
polygon,
base,
avalanche,
arbitrum
asset
enum<string>
required

Asset sent to the deposit destination

Available options:
USDC
Example:

"USDC"

quoteType
enum<string>
required
Available options:
exact_input,
exact_output
amountUsd
string
required

Requested USD amount as a decimal string

Example:

"100.00"

priority
enum<string>
required
Available options:
normal,
high
customerContext
object

Optional partner-provided customer context. Maximum 8192 encoded UTF-8 bytes. Missing, unrecognized or unsupported fields do not block preparation. Do not send credentials or bank data.

feeSubsidy
object
clientNetwork
object

Response

Response for status 200

preparationId
string
required

Opaque public preparation identifier

Example:

"prep_01JV7Q8M4Y8K6N2Z5P3R1T9W0X"

kind
enum<string>
required
Available options:
deposit_authorization
expiresAt
string<date-time>
required
messageVersion
enum<string>
default:v1
required

Identifies the authorization template that produced message. Spritz selects it server-side from the integrator; clients cannot request one. Display message verbatim and submit the preparation unchanged.

Available options:
v1,
fomo_v1
Example:

"v1"

message
string
required

Display-ready ACH authorization message

summary
object
required
submissionToken
string

Short-lived, preparation-bound bearer capability returned for integrator preparations. Send it only to the authorizing client, which uses it to submit this preparation directly to Spritz.

Example:

"ach_submit_eyJhbGciOiJIUzI1NiJ9..."