February 2026

Create Limit API Behavior Change

Changed

• Create Spend Limit endpoint https://docs.straitsx.com/v1-CARDS/reference/create-spend-limit : Added validation to prevent updating existing spend limits. The endpoint now returns a 409 Resource Conflict with code XFC409001 error when attempting to create a spend limit that already exists.

Migration Guide

• If you were previously using the Create Spend Limit API to update existing limits, you must now use the dedicated Update Spend Limit endpoint instead.
• Check for Resource Conflict responses and handle them appropriately in your integration.
• To update an existing spend limit, use https://docs.straitsx.com/v1-CARDS/reference/update-spend-limit instead.

January 2026

December 2025

2025.12.24

Card Management and Transaction

• To enhance flexibility and better support different acquirer PIN flows, we now support both 4-digit and 6-digit PINs.

Note

Action required (Non-PCI merchants):

If you want to support 4-digit PINs, please update your PIN setup / PIN change input template to use a 4-digit PIN pad when users set or update their PIN.

PCI-compliant merchants: You may encrypt and submit a 4-digit PIN directly via our PIN setup or PIN reset APIs. No changes are required if you continue using 6-digit PINs.

2025.12.22

Card Management

• Added List Merchant BIN endpoint to view all available BINs and associated card products for your issuing group.
  • Merchant BIN indicates the starting and end range of your card program
• Added a Create Card Product endpoint to create new card products with custom embossing file name prefixes for physical card designs.
• Enhanced Card Configuration Update endpoint to allow updating card product designs before printing, as well as modifying the embossing name.

Note

• Card design changes and embossing name are only permitted before a card is scheduled for printing. New card product can reuse the same merchant bin.
• API documentation will be updated following deployment.

2025.12.15

Remote Host Authorization

• CVV2 verification results are now included in the metadata section of RHA calls for improved risk handling and issuer verification visibility.

Settlement

• settlement_summary Webhook now includes the total_atm_decline field when applicable.
• New settlement_offset webhook event has been added to notify you whenever a settlement offset occurs, allowing for improved tracking of credits and debits.

General

• All changes are additive and backwards compatible. Review your integration to ensure new fields and webhooks do not affect existing processing logic.