API Overview

Cybersource Product Notes

Announcements
- Important: SCMP Now Requires HTTPS
- Important: SOAP Toolkit Update
- Bin Lookup Service 2.0
- Upcoming Change to Cybersource Customer Support Email Notifications
- Payer Authentication Migration
- New Boarding Validation Rules

Features Released in January and Febuary
- Enabling Multiple Captures with One Authorization on the SIX Processor
- Enabling Split Shipments on the Chase Paymentech Salem Processor
- Merchant Boarding Support for OmniPay Direct Processors on Visa Acceptance Platform
- Support Display of Alternative Payments Line Items in Reseller Invoices and Reporting
- Microform Support for US ACH/eCheck
- Adding a Mastercard Identifier to Transaction Search and Details
- Added Support for the ProviderTransactionID Field
- Flex Microform Simplified PCI 4.0 Compliance
- Kernel in the Cloud Certification to the MPoC Standard
- Message-Level Encryption Support
- Digital Accept Enables Debit or Credit Routing in Brazil
- Enabling Saved Cards on Digital Accept Platforms
- Enabling the Tokenization of Account Funding Transactions
- Business Center Searches for Merchant Reference ID
- Pilot Launch of AI-Generated Transaction Summary on Transaction Details Page
- Support for Mastercard’s MIT Framework Added to the Cielo Processor
- Support for Mastercard’s MIT Framework Added to the Rede Processor
- Oracle Commerce Cloud Microform Upgrade
- Commercetools Microform Upgrade
- Salesforce B2C Commerce REST Microform Upgrade
- Salesforce B2C Commerce SOAP Microform Upgrade
- PrestaShop Microform Upgrade
- Paze Wallet Boarding Automation Added for Partners
- Updates Prosa to Support Merchant-Initiated Transactions
- Rule-Based Routing

Payer Interface Upcoming Features
- Click to Pay and Unified Checkout Support for the Brazilian Market
- Click to Pay to Support Automatic Cardholder Details Lookup
- Moving Name Details in Unified Checkout and Pay by Link
- Flex Microform and Unified Checkout Added 8-Digit Card Number Prefix
- Paze to be Added to Invoicing and Pay by Link
- Customers Will Be Transitioned to the Upgraded Recurring Billing Service
- Echeck Token Support on Virtual Terminal
- Boarding Enhancements for Virtual Terminal
- Pay by Link Receipts
- Invoice Payment Status Updates
- Invoicing Email and Webhook Notifications
- New Customer Support Role for Pay by Link Resellers
- Bank Identification Number to Be Returned in API Response of Tokenized Payments
- Click to Pay Registered User Feature
- eCheck to be Added to Invoicing and Pay By Link
- Pay By Link Merchant Branding
- Account Funding Transactions to be Supported Through Streamline
- New Mastercard Transaction Link Identifier Field
- Account Verification Will Now Support Anticipated Amount
- Audit Logging to be Enabled for Invoicing and Pay by Link
- Custom Merchant-Defined Data Added to Invoicing
- Microform Payment Credential Retrieval
- Invoice Webhook Events to be Enabled Without Payer Confirmation Email
- Enabling SCA Exemptions on Streamline
- PINless Debit to Be Enabled for China UnionPay
- Enabling 3-D Secure for Card-Not-Present Transactions on the EFTPOS Gateway
- Invoicing to Enable Merchants to Override Field Labels
- Network Tokens Being Added to Boarding Templates
- Recurring Billing Will No Longer Require a Zero Amount Authorization
- Classic Analytics Dashboard Reaching End of Life
- Microform to Extend Target Origins

Payment Processing Upcoming Features
- Account Funding Transactions Available on the OmniPay Direct Processor
- Updating FDC Compass Level II and Level III Processing to the June 2024 Specification
- AFT Transactions Available on the FDC Nashville Global Processor
- Adding Mastercard Processing on Visa Platform Connect in Colombia
- Support for Card Present Retail Contactless Transaction for ITMX
- Elavon to Support the Mastercard Mandate to Populate the Merchant Payment Gateway ID
- Account Funding Transactions Available on the Streamline Processor
- Support for Visa Card Payments on Apple Pay Available on the JCN Gateway
- Card Present Connect Adding Lodging and EV Functionality
- Purchase Return Authorization to be Enabled on Omnipay Gateways
- Account Funding Transactions to be Supported Through Omnipay
- Mobile Fuel Purchases Can Be Processed with Unified Checkout on a Phone
- Prisma Connection to Support 3-D Secure 2.0, Network Tokens and Merchant-Initiated Transactions
- Updates Prosa to Support Merchant-Initiated Transactions
- Rule-Based Routing

Post Processing Upcoming Features
- Generating Reports with eCheck Transaction via Reporting API

Visa Acceptance Platform Upcoming Features
- Merchant Boarding Enhancements
- Network Tokens Being Added to Boarding Templates
- Adding Mastercard Processing on Visa Platform Connect in Colombia
- Transaction Verification Based on Anticipated Amounts
- Auto-Generation of Organization IDs

Risk Management Upcoming Features
- New Fields for Decision Manager Users Subscribed to Elephant
- Increase the Number of Custom Fields That Can Be Used
- Velocity Tracking for Payment Account Reference
- Decision Manager for Portfolios Pilot Launch
- Add the Parent ID to Case Management Details
- New Declined Payment Status in Fraud Management Essentials

Upcoming Technical Partner Updates
- SAP Commerce Cloud Microform Upgrade
- Salesforce B2B Microform Upgrade
- Adobe Commerce Legacy Build Microform Upgrade
- New SAP DPA Field Authorization By DigitalPaytSrvc

On This Page

Flex Microform and Unified Checkout Added 8-Digit Card Number Prefix

Products Included:

Flex Microform

Unified Checkout

Region/Country:
Global

Expected Release Date:
March 2025

Internal Epic Number:
20531

Flex Microform and Unified Checkout will now support 8-digit card number prefixes. A new optional

transientTokenResponseOptions.includeCardPrefix

REST field will enable users to select whether the Capture Context returns a 6-digit, 8-digit, or no card number prefix. To select the type of card number prefix:

No field included: A 6-digit prefix is returned. (default)

true

: An 8-digit prefix is returned.

false

: No prefix is returned.

The following conditions apply:

8-digit card number prefixes apply only to Discover, JCB, Mastercard, UnionPay, and Visa brands with 16-digit card numbers or more.

Any card with fewer than 16 digits will return a 6-digit prefix even when the

transientTokenResponseOptions.includeCardPrefix

field is set to

true

.

Any card brand other than Discover, JCB, Mastercard, UnionPay, or Visa will return a 6-digit prefix even when the

transientTokenResponseOptions.includeCardPrefix

field is set to

true

.

If any card brand is co-branded with Discover, JCB, Mastercard, UnionPay, or Visa, an 8-digit prefix will be returned if the

transientTokenResponseOptions.includeCardPrefix

field is set to

true

.

IMPORTANT

If your application does not require a card number prefix for routing or purposes, set the

transientTokenResponseOptions.includeCardPrefix

field to

false

. This will minimize your personal data exposure.

For more information on 8-digit prefixes, see: 8-digit-bins-and-pci-dss-what-you-need-to-know

Customer Impact

Merchants will need to determine the correct card number prefix format to use with their payment system. If no decision is made, the current 6-digit format will continue to be used for all cards and card lengths.

Back to top