> ## Documentation Index
> Fetch the complete documentation index at: https://developer.fin.com/llms.txt
> Use this file to discover all available pages before exploring further.

# July 14, 2026

> Changelog for July 14, 2026

## 🛠️ Improvements

### Crypto Orchestration

1. **`status` Field Added to [Get Customer Wallets](https://developer.fin.com/api-reference/customers/get-customer-wallets)** `GET /v2/customers/{customer_id}/wallets` responses now include a `status` field (`PENDING`, `ACTIVE`, `INACTIVE`) on each wallet object, reflecting the same asynchronous provisioning state introduced by the new Create Customer Wallets endpoint. `address` is `null` until the wallet finishes provisioning.

### Payment Instructions

1. **Pay-in Endpoints Temporarily Unavailable** `POST /v2/transactions/pay-ins`, `GET /v2/transactions/pay-ins`, and `GET /v2/transactions/pay-ins/{payin_id}` are temporarily unavailable. They are expected to return in the first week of August 2026.

## ✨ New Features

### Virtual Accounts

1. **Additional Fiat Currencies and Rails on** [Create Virtual Account V2](https://developer.fin.com/api-reference/virtual-accounts/create-virtual-account-v2)`POST /v2/customers/{customer_id}/virtual-accounts` now accepts `EUR` and `MXN` in `source.currency` (previously `USD` only), and `FEDNOW`, `SEPA`, and `SPEI` in `source.rail` (previously `ACH`, `SWIFT`, and `FEDWIRE` only). The endpoint description has also been updated to describe general fiat-to-crypto conversion rather than USD-to-USDC specifically.

### Crypto Orchestration

**New Endpoint:** [**Create Customer Wallets**](https://developer.fin.com/api-reference/customers/create-customer-wallets)`POST /v2/customers/{customer_id}/wallets` Provision one or more crypto wallets for a customer in a single request. Specify one or more `rail`/`currency` pairs in the `wallets[]` array; each requested wallet is created asynchronously and starts with a status of `PENDING`, moving to `ACTIVE` (or `INACTIVE`) once the wallet address has been issued. Poll `GET /v2/customers/{customer_id}/wallets` to check on status.

* Returns a `409` if any requested `rail`/`currency` pair already exists for the customer, listing the colliding pairs in the response
* Currently supports `POLYGON` → `USDC`, `ETHEREUM` → `USDC`, and `SOLANA` → `USDC`