1. Change Log
VM_API
English
  • 简体中文
  • English
  • Integration Guide
  • Environment Configuration
  • Global Error Codes
  • Transaction Type Description
  • Card Status Description
  • Webhook Signature Verification
  • VM Card operation
    • Get Account Balance
      POST
    • Get Card Product Code
      POST
    • Apply for Card
      POST
    • Card Details
      POST
    • Modify Card Limit(For credit line cards only)
      POST
    • Freeze/Unfreeze Card
      POST
    • Card Top-up(For prepaid cards only)
      POST
    • Card Refund(For prepaid cards only)
      POST
    • Transaction Records
      POST
    • Delete Card
      POST
    • Card List
      POST
    • Card Flow
      POST
  • Notification
    • WebHook
    • Card 3DS Notification
  • Change Log
    • Change Log
  • FAQ
    • FAQ
  • Get accessToken
    GET
  • 数据模型
    • 示例数据模型
      • Pet
      • Category
      • Tag
  1. Change Log

Change Log

This changelog records each VM API change. Updates are listed in chronological order, including additions, updates, and removals, helping developers understand version differences and complete API integration.

2026-08-26#

Webhook Security Enhancement#

We have added RSA-SHA256 signature protection to VM Webhook notifications.
Each Webhook request includes a Base64-encoded signature in the X-VM-SIGN header.
The signature is generated from the exact original HTTP request body.
Merchants can verify the signature using the VM public key.
Webhook business fields and payload formats remain unchanged.
Sandbox and Production use separate VM public keys, which are provided through a controlled channel.

2026-08-05#

Overview#

This release introduces vm_card_id, the VM-generated dedicated card ID.
For backward compatibility, card_id is still supported in this release, but it will be gradually deprecated in future versions. New integrations should use vm_card_id first.

API Changes#

New vm_card_id request support#

The following endpoints now accept vm_card_id for card lookup or operations:
POST /cardDetail
POST /deleteCard
POST /freezeCard
POST /rechargeCard
POST /refundCard
POST /cardTransaction
POST /updateCardLimit
POST /getCardList
POST /getCardFlow

New vm_card_id response field#

The following endpoints now return vm_card_id in the response:
POST /createCard
POST /cardDetail
POST /cardTransaction
POST /getCardList
POST /getCardFlow

Notes#

card_id remains available for compatibility with existing integrations.
If both card_id and vm_card_id are provided, they must refer to the same card.
vm_card_id is the VM-specific card identifier and will become the primary identifier over time.
No non-card endpoints were changed in this release.

Webhook / Callback#

If your integration consumes VM webhook or callback messages, the payload will also include vm_card_id so downstream systems can standardize on the VM card identifier.

2026-06-09#

To improve the external integration capabilities of the VM API, this release includes the following updates:

Added#

Added support for a custom client request identifier. Developers can pass X-Client-Request-Id in the request header for request tracking, duplicate request identification, and log correlation. If this header is provided in the request, the same X-Client-Request-Id will also be returned in the response header.
Added a new card flow query API: /getCardFlow.

Updated#

The /getProductCode API response now includes a new field: remaining_open_card_num, which indicates the remaining number of cards that can be issued under the current product code.

Change Details#

TypeAPI/CapabilityChange
AddedCustom X-Client-Request-IdSupports passing a custom request identifier in the request header. If provided, the same value will be returned in the response header.
Added/getCardFlowAdded a new API for querying card flow records.
Updated/getProductCodeAdded remaining_open_card_num to the response.

Request Header#

HeaderRequiredDescription
X-Client-Request-IdNoA custom request identifier. If the same value is submitted repeatedly under the same application, Duplicate Client Request Id will be returned.

Response Header#

HeaderDescription
X-Client-Request-IdIf X-Client-Request-Id is provided in the request header, the same value will be returned in the response header.
修改于 2026-08-27 01:27:18
上一页
Card 3DS Notification
下一页
FAQ
Built with