Overview

We have updated our API documentation to introduce new functionality and improve clarity for existing integration flows:

1. New Enhancement: Added custom payment description support to improve processing flow with recipient banks.
2. Documentation Improvements: Updated FAQs, callback event references, and API specifications to reflect the latest system behaviors.

Part 1: New Enhancement

We’ve added support for the paymentReason field in both the Customer Profile Bank Account and Payout Recipient APIs.

📘

Payment reason is a field used to pass clear, specific instructions to the receiving bank. It is sent as the payment description to the bank and will override the Remittance Information (MT103 Field 70 / pacs.008 Remittance Information) in the payment message.

Endpoints:

• POST /v1/customer_profile/{customer_profile_id}/payout-recipients
• PATCH /v1/customer_profile/{customer_profile_id}/payout-recipients/{recipient_id}
• GET /v1/customer_profile/{customer_profile_id}/payout-recipients/{recipient_id}
• GET /v1/customer_profile/{customer_profile}/payout-recipients
• POST /v1/payout-recipients
• PATCH /v1/payout-recipients/{recipient_id}
• GET /v1/payout-recipients/{recipient_id}
• GET /v1/payout-recipients

Endpoints:

• POST /v1/customer_profile/{customer_profile_id}/bank_accounts
• PUT /v1/customer_profile/{customer_profile_id}/bank_accounts/{bank_account_id}
• GET /v1/customer_profile/{customer_profile_id}/bank_accounts

Part 2: Documentation Improvements

1. Guides > FAQs

• Bank Account FAQs: Updated Question 2 to include the new callback event cpbaVerificationStatusUpdated.
• Swap FAQs: Updated Question 1 to include XSGDUSDT swap pair.

2. Guides > Resources > Webhook / Callbacks > Callback Samples

• Deposit/Payment Callbacks: Added description on the payment transactions payload structure.
• Blockchain Deposit and Withdrawal Status Update Callbacks: Added callback sample for the Blockchain Deposit Status Update.
• Added new callback samples for Customer Profile Bank Account Callbacks.

3. API Reference

• Get Account Statement API: Updated the query parameter filter[currency] to allow sgd and usd currency filtering options.
• Webhook APIs: Updated the Get webhooks and Update webhooks API to include below events.
  • cpbaVerificationStatusUpdated
  • cpbaCreated
  • ubaCreated
  • ubaVerificationStatusUpdated
• Update Transaction Limit API: Updated the response schema to include customerProfileId attribute.
• Get Supported Swap Pairs API: Updated the response sample data to include XSGDUSDT swap pair.
• Create a First Party Bank Transfer Payout API: Updated the request schema attribute purpose_code description to include applicability for payments to UAE (in addition to SGD FAST payouts), and added validation for alphanumeric values up to 6 characters.

🚨 IMPORTANT: Action required by 30 Jan 2026

Starting 30 Jan 2026, we are enforcing stricter API validations to ensure SWIFT/ISO 20022 compliance. Please update your integration to the new field requirements before the deadline to avoid failures.

Overview

We are updating our API to align with downstream banking networks and introduce new withdrawal capabilities. These changes are divided into two parts:

1. Validation Updates: Stricter character and length limits for Customer Profiles.
2. New Features: Enhanced logic for Blockchain Withdrawals.

Part 1: Validation & Compliance Updates

• Goal: Reduce downstream rejections and meet ISO 20022 standards.
• Change: Stricter Regex patterns (SWIFT characters) and reduced field lengths.

1. Personal CP Configuration

Endpoints:

• POST /v1/kyc/customer_profiles

• PUT /v1/kyc/customer_profiles/:unique_id

• PATCH /v1/sandbox/kyc/customer_profiles/:unique_id Includes updates to general personal details and standard address fields.

  Parameter	Old Validation	New Validation
  customerName	Max 191 (Any chars) (Mandatory field)	SWIFT Chars (Max 50) /^(?=.{1,50}$)[a-zA-Z0-9 ]+$/ (Mandatory field)
  address.street	Max 180 (Any chars) (Mandatory field)	SWIFT Chars (Max 180) /^(?=.{1,180}$)[a-zA-Z0-9\-?:().,' +]+$/ (Mandatory field)
  address.city	Max 100 (Specific chars) (Optional field)	SWIFT Chars (Max 20) /^(?=.{1,20}$)[a-zA-Z0-9\-?:().,' +]+$/ (Mandatory field)
  address.state	Max 35 (SWIFT chars) (Optional field)	SWIFT Chars (Max 15) /^(?=.{1,15}$)[a-zA-Z0-9\-?:().,' +]+$/ (Optional field)

  
  

2. Business CP Configuration

Endpoints:

• POST /v1/kyc/customer_profiles

• PUT /v1/kyc/customer_profiles/:unique_id

• PATCH /v1/sandbox/kyc/customer_profiles/:unique_id Includes updates to general business details and standard address fields.

  Parameter	Old Validation	New Validation
  customerName	Max 191 (Any chars) (Mandatory field)	SWIFT Chars (Max 50) /^(?=.{1,50}$)[a-zA-Z0-9 ]+$/ (Mandatory field)
  address.street	Max 180 (Any chars) (Mandatory field)	SWIFT Chars (Max 180) /^(?=.{1,180}$)[a-zA-Z0-9\-?:().,' +]+$/ (Mandatory field)
  address.city	Max 100 (Specific chars) (Optional field)	SWIFT Chars (Max 20) /^(?=.{1,20}$)[a-zA-Z0-9\-?:().,' +]+$/ (Mandatory field)
  address.state	Max 35 (SWIFT chars) (Optional field)	SWIFT Chars (Max 15) /^(?=.{1,15}$)[a-zA-Z0-9\-?:().,' +]+$/ (Optional field)
  placeOfBiz	Max 255 (Any chars) (Mandatory field)	SWIFT Chars (Max 255) /^(?=.{1,255}$)[a-zA-Z0-9\-?:().,' +]+$/ (Mandatory field)

3. Personal CP+ Configuration

Endpoints:

• POST /v1/kyc/customer_profiles

• PUT /v1/kyc/customer_profiles/:unique_id

• PATCH /v1/sandbox/kyc/customer_profiles/:unique_id Includes updates to personal identity fields and standard address fields.

  Parameter	Old Validation	New Validation
  customerFirstName	Max 191 (Any chars) (Mandatory field)	SWIFT Chars (Max 50) /^(?=.{1,50}$)[a-zA-Z0-9 ]+$/ (Mandatory field)
  customerLastName	Max 191 (Any chars) (Mandatory field)	SWIFT Chars (Max 50) /^(?=.{1,50}$)[a-zA-Z0-9 ]+$/ (Mandatory field)
  address.street	Max 180 (Any chars) (Mandatory field)	SWIFT Chars (Max 180) /^(?=.{1,180}$)[a-zA-Z0-9\-?:().,' +]+$/ (Mandatory field)
  address.city	Max 100 (Specific chars) (Optional field)	SWIFT Chars (Max 20) /^(?=.{1,20}$)[a-zA-Z0-9\-?:().,' +]+$/ (Mandatory field)
  address.state	Max 35 (SWIFT chars) (Optional field)	SWIFT Chars (Max 15) /^(?=.{1,15}$)[a-zA-Z0-9\-?:().,' +]+$/ (Optional field)

4. Business CP+ Configuration

Endpoints:

• POST /v1/kyc/customer_profiles

• PUT /v1/kyc/customer_profiles/:unique_id

• PATCH /v1/sandbox/kyc/customer_profiles/:unique_id Includes updates to operating addresses, beneficial owners, and trader details.

  Parameter	Old Validation	New Validation
  customerName	Max 191 (Any chars) (Mandatory field)	SWIFT Chars (Max 50) /^(?=.{1,50}$)[a-zA-Z0-9 ]+$/ (Mandatory field)
  address.street	Max 180 (Any chars) (Mandatory field)	SWIFT Chars (Max 180) /^(?=.{1,180}$)[a-zA-Z0-9\-?:().,' +]+$/ (Mandatory field)
  address.city	Max 100 (Specific chars) (Mandatory field)	SWIFT Chars (Max 20) /^(?=.{1,20}$)[a-zA-Z0-9\-?:().,' +]+$/ (Mandatory field)
  address.state	Max 35 (SWIFT chars) (Mandatory field)	SWIFT Chars (Max 15) /^(?=.{1,15}$)[a-zA-Z0-9\-?:().,' +]+$/ (Mandatory field)
  operatingAddress.street	Max 180 (Any chars) (Mandatory field)	SWIFT Chars (Max 180) /^(?=.{1,180}$)[a-zA-Z0-9\-?:().,' +]+$/ (Mandatory field)
  operatingAddress.city	Max 100 (Specific chars) (Optional field)	SWIFT Chars (Max 20) /^(?=.{1,20}$)[a-zA-Z0-9\-?:().,' +]+$/ (Mandatory field)
  operatingAddress.state	Max 35 (SWIFT chars) (Mandatory field)	SWIFT Chars (Max 15) /^(?=.{1,15}$)[a-zA-Z0-9\-?:().,' +]+$/ (Mandatory field)
  beneficialOwners[].address.street	Max 180 (Any chars) (Mandatory field)	SWIFT Chars (Max 180) /^(?=.{1,180}$)[a-zA-Z0-9\-?:().,' +]+$/ (Mandatory field)
  beneficialOwners[].address.city	Max 180 (Any chars) (Mandatory field)	SWIFT Chars (Max 20) /^(?=.{1,20}$)[a-zA-Z0-9\-?:().,' +]+$/ (Mandatory field)
  beneficialOwners[].address.state	Max 180 (Any chars) (Mandatory field)	SWIFT Chars (Max 15) /^(?=.{1,15}$)[a-zA-Z0-9\-?:().,' +]+$/ (Mandatory field)
  trader.address.street	Max 180 (Any chars) (Mandatory field)	SWIFT Chars (Max 180) /^(?=.{1,180}$)[a-zA-Z0-9\-?:().,' +]+$/ (Mandatory field)
  trader.address.city	Max 180 (Any chars) (Mandatory field)	SWIFT Chars (Max 20) /^(?=.{1,20}$)[a-zA-Z0-9\-?:().,' +]+$/ (Mandatory field)
  trader.address.state	Max 180 (Any chars) (Mandatory field)	SWIFT Chars (Max 15) /^(?=.{1,15}$)[a-zA-Z0-9\-?:().,' +]+$/ (Mandatory field)

Part 2: New Features (Blockchain Withdrawals)

• Goal: Allow users to keep funds in fiat (SGD/USD) without auto-conversion.

1. Blockchain Withdrawal Improvements

Endpoint:

• POST /v1/blockchain_transfer/withdrawals/

  We've introduced a new field when creating a blockchain withdrawal request. Depositing SGD/USD into the Dashboard VAs will now go towards your SGD/USD balances instead of being auto-converted to XSGD/XUSD. You can now select which balances to deduct for each blockchain withdrawal.
  Note: Once you've made the necessary changes, please let our internal team know for us to roll out the new dashboard updates.

  New Parameter	Description	Accepted Values
  wallet_source	The source of funds the deduction will be made from. If no value is specified for this field, XSGD and XUSD withdrawals will, by default, be deducted from the XSGD and XUSD balances respectively. This field is Optional	XSGD XUSD USD SGD

We have published three new endpoints to support user withdrawals from their StraitsX account via API

• GET /v1/withdrawals/bank-accounts
• POST /v1/withdrawals
• GET /v1/withdrawals/:withdrawal_id

You will be able to make a withdrawal from your XSGD or XUSD wallet to a verified bank account on your StraitsX account easily with these two new endpoints.

We are now supporting both the SHA and OUR charge option for USD first party withdrawals (SWIFT) via POST /v1/customer_profile/{customer_profile_id}/withdrawals. The default charge option will be SHA if the attribute is not provided in the request.

We have now introduced the ability to create a customer profile bank account that's meant for SWIFT transactions. This means that the POST /v1/customer_profile/{customer_profile_id}/bank_accounts now supports the following optional fields:

• swift_bic
• intermediary_swift_bic
• routing_code

We released a new endpoint GET /v1/payout-recipients/requirements that allows you to query for the recipient's data requirements depending on the recipient's country, currency, the disbursement method, the proxy type (when disbursement method is paynow) and the entity type. The data requirements are returned in regex and you can apply the same validation on your platforms to support recipient creation.

Note that if you are using the regex in a programming language that requires double backslashes (like Ruby or Java), then the response is already the correct regex. However, if you are using it directly in a regex engine (like JavaScript or Python), you would need to replace the double backslashes \\ with single backslash \.

For added convenience, you can now also query and update webhooks for the various supported events directly via the following endpoints:

• GET /v1/webhooks
• PATCH /v1/webhooks

Updating webhooks via the StraitsX dashboard continues to be available to you.

When creating a payout recipient via POST /payout-recipients you now also have to pass in the following required fields:

• recipientInformation.entityType
• recipientInformation.currency

We now also support creating a SWIFT payout recipient (with additional required fields) to allow for payouts in USD.

For more information, check out the API reference here.

We are excited to announce that we now support passing in purpose code for all SGD withdrawals and payouts via FAST. This field is optional and will be defaulted to OTHR (Others) if omitted. Full list of supported purpose codes can be found here.

Enhanced Endpoints:

• POST /customer_profile/{customer_profile_id}/withdrawals
• POST /customer_profile/{customer_profile_id}/payouts
• POST /payouts

We’re thrilled to announce the launch of StraitsX API v1.1.0, a new version that introduces the highly requested third party and regular transfers capabilities to our API suite. With this release, we now officially support three different integration models, depending on your business profile and requirements:

• First Party Transfer (Customer Profile)
• Third Party Transfer (Customer Profile)
• Regular Transfer

Detailed integration flows are now included in the revamped Guides section and all relevant endpoints have been updated in the API Reference section. If you are unsure or need clarification, contact us.

Other changes

• We have made some underlying improvements on how we handle FX rates and network fee estimation for our Blockchain and Swap API and removed the rate limit error on these endpoints
• Added two optional fields for POST /v1/customer_profile/{customer_profile_id}/withdrawals to support overseas withdrawals:
  • routing_code: Maximum 31 char alphanumeric
  • intermediary_swift_bic: Maximum 11 char alphanumeric