Debit
Customer selects debit when available, reviews the provider-owned checkout, and authorizes the quoted purchase. This does not add money to the USD balance.
How money moves
Every route has a different sequence.
Cash loading, wire, ACH, debit, credit, selling, and swapping are separate journeys. This page shows the high-level roles and state changes without implying that every provider or product is always available.
Retail cash
Paper cash becomes a USD balance before any Bitcoin purchase.
Participating retailers accept a cash load. They do not sell Bitcoin through the Bitcoin POP flow.
01CustomerGenerates a secure retail barcode.
02Participating retailerAccepts the paper-cash load using the barcode.
03Cash-loading routeProcesses the load under applicable limits and requirements.
04USD balanceCash load posts to the Crypto Dispensers USD balance.
05Separate purchaseCustomer separately reviews and authorizes a Bitcoin purchase.
Other purchase routes
A checkout is not the same as adding cash.
Debit, credit, ACH, and wire have route-specific providers, requirements, instructions, timing, limits, fees, and review states.
Credit
Credit is a distinct availability and checkout path. The customer reviews the current provider terms before authorizing.
Bank ACH
Eligible customers use the bank-transfer route and review current authorization, provider, timing, and fee details.
Wire transfer
A customer submits a request and sends funds only after receiving approved instructions for that specific request.
Provider responsibility matrix
Who does what should not be guessed.
This matrix states public high-level roles. Provider names and exact responsibilities should be added only when contracts permit disclosure and the current architecture is verified.
| Function | Crypto Dispensers | Applicable provider or retailer | Customer |
|---|---|---|---|
| Account interface | Presents route information and account steps. | May provide a secure route-specific checkout or service. | Selects the intended action. |
| Identity information | Oversees the account and applicable review. | May supply verification services under the applicable route. | Provides accurate information. |
| Retail cash collection | Provides the account and barcode flow. | Participating retailer accepts the cash load; applicable provider processes it. | Provides cash and the correct barcode. |
| Payment authorization | Presents the available route and next step. | Processes the applicable payment service. | Reviews and authorizes. |
| Wallet destination | Shows the destination and network step where applicable. | May support execution or delivery under the route. | Confirms wallet address, network, and control. |
| Monitoring and review | Maintains compliance and fraud-review responsibilities. | May apply route-specific controls and share relevant signals. | Responds truthfully to requests for information. |
Transaction-state discipline
Requested is not received. Received is not delivered.
Public copy and support must preserve the difference among a customer request, provider acknowledgment, funds received, compliance review, fulfillment, customer delivery, revenue, and settlement.
Request
The customer expressed intent or submitted information. No funds or fulfillment are implied.
Funds received
An authoritative record confirms receipt through the applicable route. This does not by itself prove Bitcoin delivery.
Under review
A compliance, fraud, operations, or provider review remains open.
Delivered or settled
Use only when the authoritative lifecycle establishes the specific outcome being described.