🚀 API Update v2.3.7 is now live in Production! 🎉

This release introduces JPY off-ramps, improves fee management with batch updates, enhances user communications with transactional emails, upgrades the webhook system, and simplifies beneficiary schemas.

✨ What’s New

🇯🇵 JPY off-ramps now available
💰 Batch fee updates (multi-user support)
🧹 Simplified beneficiary schemas
🔔 New webhook system (multiple endpoints & improved reliability)
⏳ Improved beneficiary creation handling
📧 Transactional emails (ACH Pull & bank linking)

🇯🇵 JPY Off-Ramps

JPY is now supported for off-ramp flows.

You can create JPY beneficiaries via:

POST /user/bank-account/remote

💰 Batch Fee Updates

You can now configure fees for multiple users in a single API request.

Previously, fees had to be updated one user at a time, requiring multiple API calls.
With this update, you can apply the same fee configuration across many users in one request.

What’s Improved

✅ Apply fees to multiple users at once
⚡ Reduce the number of API calls required
🧩 Supports wildcard configurations (e.g. output_currency = null)

🔔 Webhook System Upgrade

We’ve introduced a new webhook system with improved flexibility and reliability.

What’s New

Configure multiple webhook endpoints per merchant
Each event is delivered independently to all endpoints
Failures on one endpoint won’t affect others
Option to subscribe endpoints to specific event types
Full API-based management (create, update, delete, rotate secrets)

Reliability Improvements

Endpoints that consistently fail are automatically disabled
You’ll receive an email notification if this happens
You can re-enable them by updating the endpoint

⚠️ Backwards Compatibility

Existing webhook configurations continue to work.

Updating webhook URL/secret via the merchant endpoint will be deprecated in a future release.
We recommend migrating to the new webhook endpoints.

⚠️ Backwards Compatible Changes

Beneficiary Schema Simplifications

The following fields have been removed from specific beneficiary schemas:

account_type removed from: INR, MXN, TRY, PHP, IDR, PKR
bank_code and bank_subcode removed from: TRY, PHP, IDR

These fields were not used by downstream providers and are no longer required.

If your integration still sends these fields, they will be ignored, but we recommend updating your payloads.

⏳ Beneficiary Creation Handling

Destination bank account creation supports both immediate and asynchronous processing.

Most requests will return an ACTIVE status immediately
In some cases, a PENDING status may be returned initially

If a destination bank account is PENDING, you can track its status via:

GET /user/bank-account/remote/{account_uuid}

We recommend handling both statuses in your integration.

📧 Transactional Emails (ACH Pull & Bank Linking)

We now support transactional emails for key user actions:

ACH Pull transfers (USD only)
Bank account linking / unlinking via Plaid

Delivery Modes

DTR-managed emails: DTR sends emails directly to end users using predefined templates
Merchant-managed emails: You receive the event and send the email yourself

Default templates are provided by Bakkt.
If using DTR-managed emails, you can also provide your own HTML templates.

👉 This gives you flexibility to either rely on DTR-managed communications or fully control your user messaging.

🙌 Let us know if you need help integrating these updates!