API Update - October 2026
We've added some new features like Multiple Session support and improved handling of intermediary banks. We've also updated currency rules and fixed several issues that caused payments to need manual repair. See below for more details.
New Feature: Multiple Session Support
StoneX Payments APIs now support multiple sessions for a single API client. Each session can carry its own commercial configuration, such as margin type, rate expiry, value date behaviour, while sharing the same client ID, credentials, credit lines and reporting.
This is useful for clients who operate several business units or serve their own commercial clients and need different pricing setups under one StoneX relationship.
To use a session, pass the new optional X-Session-Id header on the following endpoints:
You can find more details in our Multiple Session Support guide.
Benefits:
- Run multiple pricing profiles under a single client ID and set of API credentials.
- Keep credit, limits and reporting consolidated across business units.
- Sessions are set up and managed by StoneX, so no engineering work is needed on your side beyond sending the header.
Impact:
- The header is optional. If you don't send
X-Session-Id, your requests use your existing default session and you will see no change in behaviour. - A quote can only be booked on the same session it was requested on. Booking a quote under a different session will be rejected.
- Requests with a session that is not configured for your account will fail validation.
- Please contact our product team if you'd like additional sessions set up.
Currency Rule Updates
The following currency validation rules have been updated:
- MYR: Payments that contain the words "Israel" or "Tel Aviv", or the country code "IL", in any payment details will now be rejected. Our MYR correspondent banks are unable to process these payments.
- AED: AED payments to beneficiaries in the United Kingdom (GB) are now supported.
- KES: The Purpose of Payment codes
ONCLandOTHRare no longer accepted for KES payments to Kenya. The description for POP codeIBLD(4301) has also been updated. - JMD: Bank code validation has been corrected for National Commercial Bank Jamaica. The correct BIC is now
JNCBJMKX.
Impact:
- Validation API responses will reflect the updated rules. You can use the Get Currency Requirements API to check the latest rules for any currency.
Action Required:
- Clients processing MYR or KES payments should review their payment workflows to make sure requests meet the updated rules before submission.
Bug Fixes
We've also fixed several issues that caused some API payments to fall into our repair queue instead of being processed straight through.

