New Transaction Routing Endpoint Added

Added

Release Date
June 16, 2026

Products Affected
Transactions API

Impact
New endpoint added to route transactions to specified financial accounts

Audience
Customers launching multi-account card programs

Action Required
None

Overview

Lithic has launched a new API which lets customers select the specified financial account that card transactions will post to. The reference page can be seen here.

Details

Request

cURL

curl -X POST "https://api.lithic.com/v1/card_transactions/550e8400-e29b-41d4-a716-446655440000/route" \
    -H "Content-Type: application/json" \
    -H "Authorization: <AWS SigV4 signature>" \
    -d '{
      "financial_account_token": "f1a2b3c4-d5e6-47f8-9a0b-1c2d3e4f5a6b"
    }'

Successful Response

Successful response returns 202, with description: Accepted

Note that a successful response will result in a card_transaction.updated webhook, which will show the new ledgering requested.

Unsuccessful Responses

Status Message When
400 Instance is not modular secured charge Instance isn't eligible for routing
400 Card transaction has already been routed to a different financial account Endpoint has already been called for this transaction_token
404 Transaction not found transaction_token doesn't resolve to a card transaction
404 Account not found financial_account_token not owned by the instance
400 Cannot route to a closed financial account Target account is closed

Release Timeline

Available now: June 16, 2026.

User Impact

This addition has no impact to live programs. For more information on Lithic's Ledger, head to our Ledger Solutions page.

If you have any questions or concerns, please contact us via the HELP link in your Lithic Dashboard.