Added Stablecoin Payment Originations
September 11, 2026
Customers looking to send Stablecoin funds onchain
None, this change is additive only
Overview
Lithic is now able to send and receive Stablecoin payments onchain, built directly into our Payments endpoints.
Details
The Create Stablecoin Payment endpoint validates
- The originating
financial_accounthasstatus == OPENand supports Stablecoin.- See Lithic implementations to configure your Financial Accounts to support Stablecoin payments.
- The
blockchain_recipient_tokenhasverification_state == ENABLEDandstate == ENABLED. - The originating
financial_accounthas a sufficient USD balance.
Request
| Attribute | Type | Required | Notes |
|---|---|---|---|
financial_account_token | UUID | Yes | The account originating the payout. |
type | enum | Yes | PAYMENT only. Pay-ins are not initiated through this endpoint. |
amount | integer | Yes | Amount in USD cents. Strictly positive. |
blockchain_recipient_token | UUID | Yes | The recipient from POST /v1/blockchain_recipients. Must be fully enabled. Supplies the chain; the raw address is never accepted. |
token | UUID | no | Idempotency key for the payment. Generated if omitted. |
memo | string | no | Becomes the transaction descriptor. Defaults to Stablecoin payout on {chain}. |
hold | object | no | { "token": UUID } — an existing TA Hold to settle as part of the initiation. The reservation is transferred rather than balance-checked again. |
The chain of the blockchain_recipient_token drives the payout, so the request does not require the blockchain to be respecified.
Response — 202 Accepted
202 AcceptedThe standard PaymentTransaction, plus the account's balance after the hold.
| Attribute | Type | Notes |
|---|---|---|
token | UUID | The payment token — the same value used on GET /v1/payments/{token}. |
family | enum | PAYMENT. |
category | enum | STABLECOIN. |
type | enum | STABLECOIN_OUTBOUND. |
method | enum | STABLECOIN. |
method_attributes | object | StablecoinMethodAttributes — chain plus a transaction_hash that is null until settlement. |
status / result | enum | PENDING / APPROVED, or DECLINED on insufficient funds. |
direction | enum | DEBIT. |
source | enum | CUSTOMER. |
financial_account_token | UUID | The funding account. |
blockchain_recipient_token | UUID | The payout counterparty. |
external_bank_account_token | null | Always null for stablecoin. |
settled_amount | integer | 0 at initiation — nothing has settled yet. |
pending_amount | integer | The held amount, negative (funds leaving). |
currency | string | USD. Payouts are booked at par in USD cents. |
events | array | One STABLECOIN_INITIATED event at creation; later lifecycle events are appended by the stablecoin actions consumer. See Stablecoin Payment Lifecycle Guide to learn more |
descriptor | string | The memo, or the default. |
related_account_tokens | object | business_account_token / account_token connected to the financial_account |
balance | object | The funding account's balance after the hold: available_amount, pending_amount, total_amount, last_transaction_token, last_transaction_event_token. |
Errors
| Situation | Status | Message |
|---|---|---|
| Account not found, or not an account that can originate | 400 | Invalid account / Operation is not allowed for this account |
| Account not open | 400 | Invalid account status |
| Entity has no stablecoin support | 400 | Financial entity {id} does not support stablecoin |
| Recipient pending, failed screening, paused, or closed | 400 | Blockchain recipient is not enabled |
type other than PAYMENT | 422 | STABLECOIN only supports type PAYMENT; pay-ins are not initiated through this endpoint |
method supplied in the body | 422 | Extra fields are forbidden |
| Account belongs to another instance | 404 | Account not found |
| Suspended instance | 401 | Cannot perform action |
| Token reused with a different request | 409 | Stablecoin payment with token {token} already processed |
| Same token already used on a different account | 409 | Transaction group collision |
| Concurrent write on the same account | 409 | Another operation in progress. You may try again. |
Gas/Network FeesLithic does not include Gas or Network Fees as part of the originating payment. These fees are coordinated separately with your account manager.
Shared Payment Object
While the Create endpoint is different for Stablecoin payments, it is folded into the existing Get Payment and List Payments endpoints, as well as the payment.created and payment.updated webhooks.
How Stablecoin payments appear on the shared payment object
| Field | Stablecoin value |
|---|---|
method | STABLECOIN |
category | STABLECOIN |
type | STABLECOIN_OUTBOUND for a payout, STABLECOIN_INBOUND for a pay-in |
direction | DEBIT on a payout, CREDIT on a pay-in — reversed vs. ACH, matching the wire credit-transfer convention |
method_attributes | StablecoinMethodAttributes (see below) |
blockchain_recipient_token | Set on payouts, null on pay-ins |
external_bank_account_token | Always null — a stablecoin transfer has no registered bank account |
source | CUSTOMER for the public endpoint, LITHIC for Lithic-initiated payouts |
events[].type | STABLECOIN_INITIATED, STABLECOIN_REVIEWED, STABLECOIN_SENT, STABLECOIN_SETTLED, STABLECOIN_REJECTED (payout); STABLECOIN_RECEIVED (pay-in) |
StablecoinMethodAttributes
StablecoinMethodAttributesThe rail-specific block on the payment object, and the third member of the method_attributes union beside AchMethodAttributes and WireMethodAttributes. It is returned by the create endpoint and by both read endpoints, on pay-ins as well as payouts.
| Attribute | Type | Notes |
|---|---|---|
chain | string | Blockchain the transfer moves on, e.g. ETH. On a payout this is the recipient's registered chain, not something the caller supplies. |
transaction_hash | string | null | On-chain hash of the transfer — the blockchain's counterpart to an ACH trace number, and the customer's own receipt for a transfer they can already see on chain. null until the transfer settles on chain, so it is always null in the create response. |
Release Timeline
Available now: Sept 11, 2026.
User Impact
This change is additive only. Learn more about Stablecoin Payments via Stablecoin at Lithic.
If you have any questions or concerns, please contact us via the HELP link in your Lithic Dashboard.
The Lithic changelog has an RSS feed! To monitor for new update announcements, subscribe with your preferred RSS reader.