Change Log

2025-10-31 (already online)

Card opening process optimization

The original V1 version interface card activation process will not be updated; it will run in parallel with the V2 version interface.

circle-info

If you upgrade to the V2 version interface, you must use the: Create card-V2 interface Card Operation Transaction-V2 interface Card Purchase Transaction interface

Optimization Point:

  1. The card no is returned immediately after the create card interface is called.

  2. Added card purchase transaction. You can query the card fee and first-time deposit amount for your order.

  3. Create card records and first deposit records are merged.

  4. In the Card Operation Transaction-V2 interface, the value of the type field has been changed to be optional.

Old V1 Process Detail:

  1. call Create card interface [/merchant/core/mcb/card/openCard].

    1. CardNo will be returned only when the card is successfully created

    2. The response data structure is an array.

    3. "amount" Field means: card fee.

{
    "success": true,
    "code": 200,
    "msg": "Success",
    "data":
    [
        {
            "orderNo": "1852379830190366720",
            "merchantOrderNo": "T1852379826671345664",
            "cardNo": null,
            "currency": "USD",
            "amount": 5, //card fee
            "fee": 0,
            "receivedAmount": 5,
            "receivedCurrency": "USD",
            "type": "create",
            "status": "processing",
            "description": null
            "remark": null,
            "transactionTime": 1730476741729
        }
    ]
}
  1. The webhook will push Create card and Deposit card data from the card operation transaction. There are two types of data in total.

New V2 Process Detail:

  1. call Create card interface [/merchant/core/mcb/card/v2/createCard].

    1. The card no will be returned immediately.

    2. The response data structure is object.

    3. "amount" Field means: Initial Deposit amount

  1. The webhook will push Create card from the card operation transaction.

  1. if you want to see card fee. you can query /merchant/core/mcb/card/purchaseTransaction interface

2025-10-13 (already online)

  1. Card Auth Transaction interface Update

    Added response fields:

2025-10-02 (already online)

  1. Support Bins interface Update Added response fields:

    1. metadata.cardHolderMaxCardLimit (Maximum purchase quantity limit for cardholders)

    2. metadata.cardHolderModel (Cardholder business model, B2B, B2C)

    3. metadata.supportSettingNoPinPaymentAmount (Set the amount limit for password-free payment (Physical card))

    4. metadata.defaultNoPinPaymentAmount (Default amount for password-free payment(Physical card))

    5. metadata.noPinPaymentAmountMinQuota (Minimum amount for password-free payment(Physical card))

    6. metadata.noPinPaymentAmountMaxQuota (Maximum amount for password-free payment(Physical card))

    7. risk (High risk merchant. Consumption in this scenario will trigger card cancellation risk control)

  2. Card Info interface Update

    1. The response fields cardNumber, cvv, and validPeriod will be removed (2025-11-01 deprecated). Access the information separately through the [/merchant/core/mcb/card/sensitive] interface.

  3. Card Info For Sensitive interface Add

    1. The three card elements (cardNumber, cvv, expireDate) are returned separately through this interface, and the parameter values ​​are encrypted.

  4. The freeze-v1 interface will be deprecated. 2025-11-01 deprecated

    1. Use of the v2 interface /merchant/core/mcb/card/v2/freeze

  5. The unfreeze-v1 interface will be deprecated. 2025-11-01 deprecated

    1. Use the v2 interface. /merchant/core/mcb/card/v2/unfreeze

  6. Cardholder

Introduction: The cardholder-v1 API functionality has been merged into cardholder-v2 for unified access. Required parameters are determined based on the different modes.

Cardholders are divided into two modes: B2B and B2C, with different request parameters.

  • B2B corresponds to the parameters of the original Cardholder-Create-v1 API;

  • B2C corresponds to the parameters of the original Cardholder-Create-v2 API.

The B2B and B2C values ​​are the metadata.cardHolderModel returned in the corresponding /merchant/core/mcb/card/v2/cardTypes API.

If needCardHolder = true, a cardholder needs to be created.

If metadata.cardHolderModel = B2B, use the B2B mode.

If metadata.cardHolderModel = B2C, use the B2C mode.

  • Cardholder-Create-v1 will be deprecated. 2025-11-01 deprecated. (Merged into the cardholder-create-v2 interface)

Use the v2 API /merchant/core/mcb/card/holder/v2/create. The request parameters are divided into two modes: B2B and B2C.

  • Cardholder-Update-v1 will be deprecated. 2025-11-01 deprecated. (Merged into the cardholder-update-v2 interface)

Use the v2 API /merchant/core/mcb/card/holder/v2/update. The request parameters are divided into two modes: B2B and B2C.

2025-06-22 (already online)

  1. The city list interface data has been fully updated. Customers need to resynchronize, and some city codes have been adjusted;

  2. Added the city list-v2 interface, which returns the province/state/region level data;

2025-06-22 (Already online)

  1. Added Card Issuance Process, Contains the latest card opening process for card BIN 4549, and the interface is adjusted when creating a cardholder;

  2. Added CardHoder-Create-v2 interface;

  3. Added CardHoder-Update-v2 interface;

  4. Added Upload File interface;

2025-05-18 (Already online)

  1. Added Freeze - v2 interface;

  2. Added UnFreeze - v2 interface;

  3. Card Transaction interface add type FreezeUnFreeze

  4. Card Transaction Notification add type FreezeUnFreeze

2025-04-20 (Already online)

  1. Supported card bins interface is no longer maintained (API is always available); replaced by Supported card bins-v2 version;

  2. Added Card Holder notification for Specific card BIN.

2025-04-10 (Already online)

  1. Address request parameter verification adjustment for creating and updating cardholder interface.

    1. Original rule: only English characters are supported. [Special characters supported, . - /];

    2. Current rule: can only contain letters, numbers, hyphens and spaces. regex: ^[A-Za-z0-9\- ]+$

2025-03-14(Already online)

  1. Added wallet recharge interface. No need to manually place orders in the merchant backend;

  2. Added Common API module, through which you can obtain the country/region, city, and mobile phone area code dictionary;

  3. Updated the demo package, and maintained excel and java-demo;

  4. Creating a cardholder no longer requires verification of the uniqueness of the mobile phone number and email address;

  5. Cardholder mobile phone area codes support a wider range. You can update and re-pull the supported card BIN interface to obtain;

  6. Added a required parameter cardTypeId to the request parameters for creating and updating cardholders. If the same cardholder information applies for cards with different card BINs, it is recommended to create them under different cardTypes.

2024-12-17(Already online)

  1. Update Card InfoCard Balance The field usedAmount is not required to be returned;

  2. Update create cardholder to add the request field cardTypeId;

2024-12-11(Already online)

  1. Update Supported card bins to add the response field depositAmountMaxQuotaForActiveCard;

  2. Update Open Card to add the request field amount;

Last updated