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

We now support two more swap pairs on our Swap API! You can now access the following swap pairs:

• XSGDXUSD
• XSGDUSDC
• XUSDUSDC
• USDCUSDT

We have released a new endpoint for you to get your account statement and ledger for easy reconciliation. This endpoint will return all ledger items as well as the opening and closing balance of the queried period.

See the API reference here: Account Statement