RM-32919

Description
This release introduces two updates:
Merchants can retrieve BIN (Bank Identification Number) details in the Token Management System (TMS) API, for the
/tokens
 and
/tokenized-cards
 endpoints, using a new parameter.
Partners and aggregators can request an Account Funding Transaction (AFT) cryptogram for Visa Token Service (VTS) network tokens.
Audience
Clients who integrate the TMS API into their system, using
/tokens
 or
/tokenized-cards
 endpoints endpoints, for standalone network tokens.
Partners and aggregators fetching payment credentials for VTS tokens, such as cryptogram and network token details.
Benefit
Merchants can now retrieve BIN details on demand in the TMS API, supporting improved decision making and fraud prevention.
Aggregators and partners are now able to fetch AFT cryptograms for VTS network tokens using the TMS API payment credentials endpoint.
Technical Details
BIN Details for TMS:
 Merchants must update their systems to consume the new BIN details returned on a
binLookup
 object during token operations. Endpoints:
POST /tms/v2/tokens/{{tms-token-id}}/payment-credentials
POST /tms/v2/tokenized-cards?retrieveBinDetails=true
GET /tms/v2/tokenized-cards/{{tokenized-card-id}}?retrieveBinDetails=true
Returning AFT cryptogram for VTS network tokens:
 Your merchant account must be enabled for this feature. Please contact you account manager. AFT cryptogram is only supported for VTS tokens. To request an AFT cryptogram, the
paymentCredentialType
 request field must have the value
CRYPTOGRAM
. Otherwise, it will be ignored. The AFT cryptogram is returned in the
tokenizedCryptogram
 response field.
Endpoint:
POST /tms/v2/tokens/{{tms-token-id}}/payment-credentials
Request fields example:
{
    "paymentCredentialType": "CRYPTOGRAM",
    "transactionType": "AFT"
}
Important Dates
Released to production November 20, 2024.