On This Page
Features Introduced This Week
Merchant Descriptior Name | RM-44633
Merchant Descriptior Name
| RM-44633- Description
- Cybersource is updating validation for themerchantInformation.merchantDescriptor.nameAPI field. Merchants can now submit merchant descriptor names that include either the asterisk (*) or hyphen (-) character. Transactions are no longer rejected solely because these characters are included in this descriptive field.
- Mandate
- Does not apply.
- Audience
- The updated validation is available to all merchants who use themerchantInformation.merchantDescriptor.namefield.
- Benefit
- Improved merchant descriptor support.
- Technical Details
- Example:{ "merchantInformation": { "merchantDescriptor": { "name": "MERCHANT*STORE-NAME" } } }
- Important Dates
- Released to Production May 20, 2026.
New Features for Pisma | RM-44633
New Features for Pisma
| RM-44633- Description
- Merchants who use Prisma can now use 3-D Secure 2.x, Network Tokens, and MIT/COF framework data. These capabilities are available to Prisma merchants who are enabled. This update allows Prisma merchants to support tokenized and authenticated card-not-present payment flows and submit the required transaction framework data for eligible use cases.
- Mandate
- Does not apply.
- Audience
- Merchants processing in Argentina through the Prisma connection.
- Benefit
- Prisma merchants can support tokenized, authenticated, and credential-on-file card-not-present payment flows.
- Technical Details
- Supported 3-D Secure-related values include:
- pa_specification_version
- directory_server_transaction_id
- cavv
- ucaf_collection_indicator
- ucaf_authentication_data
Supported MIT/COF-related values include:- subsequent_auth_first
- subsequent_auth_reason
- subsequent_auth
- subsequent_auth_transaction_id
Supported Network Token-related value:- network_token_cryptogram
- Important Dates
- Released to Production May 20, 2026.