ACH pull into Bakkt checking (General Ledger)

Debits the user's linked external bank account and credits their Bakkt checking balance via General Ledger CreateAchPull. The destination checking account is {account_uuid} in the path. Authenticated user is taken from session or user-uuid header.

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Path Params
uuid
required

Destination Bakkt checking account UUID (GL account)

Body Params

Initiates an ACH debit from the user's linked external bank account into a Bakkt checking balance. The user is identified by the session or user-uuid header (merged as client_uuid for validation). The destination Bakkt checking GL account is the {account_uuid} path parameter on POST .../bakkt/{account_uuid}/ach-pull. Command is routed to General Ledger as CreateAchPull.

number
required

Positive amount to pull; at most two decimal places

string
required

ISO currency enum value supported by GL for this account (e.g. USD for Bakkt checking ACH pull)

uuid
required

Linked external bank account UUID to debit (from linked-bank flow)

string
enum

Receiver type for the downstream ION leg; omit to default to BANK_ACCOUNT

Allowed:
string
required

Client IPv4 or IPv6 address (required for compliance / provider rules)

uuid

Optional GL checking account when distinct from default resolution

string
length ≤ 500

Optional note stored on the ledger transaction metadata when supported

Headers
string
length ≤ 255

Optional. Unique opaque key per logical write (e.g. UUID v4). Only applies to POST/PUT on routes that support it. Max 255 characters. Scoped to the authenticated principal. Omit for legacy behavior with no idempotency.

Responses

Language
Credentials
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json