On This Page
Features Introduced This Week
RM-31065
- Description
- This release enables the retrieval of Bank Identification Number (BIN) details in Token Management Service (TMS) API responses. This release also provides the ability to delete VTS standalone network tokens using the TMStokenized-cardsAPI endpoint.
- Audience
- Clients who use instrument identifiers or payment instrument tokens.
- Clients and aggregators interacting with the TMS APItokenized-cardsendpoint.
- Benefit
- Merchants can now retrieve BIN details on demand while supporting better fraud prevention. Enhanced token management with the ability to delete VTS standalone network tokens, eliminating the need to delete the TMS token and manage network tokens separately.
- Technical Details
- Returning BIN Details on Token Operations
- New Query Parameter:retrieveBinDetails=truecan be used to retrieve BIN details on demand during token operations.
- Requires Merchant Integration Changes: Merchants must update their systems to consume the new BIN details returned on abinLookupobject during token operations.
Deleting Standalone VTS Network Tokens- Endpoint: Thetokenized-cardsendpoint now supports the deletion of standalone VTS network tokens.
- Integration Requirement: Merchants need to update their systems to utilize this new capability.
- Important Dates
- Released to production October 1, 2024.
RM-31840
- Description
- This release adds new response codes 78, 46, and 6P in the mass transit code, and will link to code 263 for both Authorization and Authorization Reversal transactions. To make the process more efficient, we've added a logic that will map a new response codes to 263 to prevent the need to manual updates.
- Audience
- Users of mass transit on Visa DC, for all card types compatible with VPC.
- Benefit
- More specific responses.
- Technical Details
- None.
- Important Dates
- Released to production October 3, 2024.