# 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](https://docs.lithic.com/reference/routetransaction).

# Details  
- Only customers who opt into this during implementation + setup will be able to route their transactions to specified accounts. Customers who were set up with automatic postings will be unaffected.
- Before customers select the specified `financial_account`, their transactions will be posted to a suspense account.
- Transactions have a number of ledger account postings that happen throughout the lifecycle. Once the endpoint is posted to for a given `transaction_token`, all previous postings for that transaction will be transferred to the specified `financial_account`
  - This will also determine the `financial_account` for all future postings for that transaction. Therefore, this is a one-time use endpoint per `transaction_token`. Subsequent calls with that `transaction_token` will be rejected.

### Request  
cURL

```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](https://docs.lithic.com/reference/post_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](https://docs.lithic.com/docs/ledger-overview) page.

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