On This Page
Features Introduced This Week
RM-31083
- Description
- This release enables you to upload a custom logo for your Acceptance Devices.
- Audience
- Users of Acceptance Devices.
- Benefit
- Merchants can now use their own branding in Acceptance Devices.
- Technical Details
- You can upload the logo in the Business Center atAcceptance Devices > Customizations.
- Important Dates
- Released to production October 7, 2024.
RM-31565
- Description
- Omnipay: this release enables independent identification of recurring Merchant-Initiated Transactions (MITs) that use the subscription and standing order types. This ensures compliance with updated Mastercard scheme rules.
- Streamline: this release enables you to include the full 3D-Secure version number (major.minor.point) for payment authorization transactions. The minimum supported 3D-Secure version is 2.2.
- Audience
- All merchants processing on Omnipay or Streamline gateways in the European Union.
- Benefit
- Omnipay: this update ensures compliance with Mastercard rules.
- Streamline: this update reduces the risk of non-compliant transactions and processing errors.
- Technical Details
- Omnipay:subsequent_auth_reason=7(subscription) andsubsequent_auth_reason=8(standing order) are supported for Mastercard transactions.
- Streamline:pa_specification_versionsupports the major.minor.point value returned from the Payer Authentication response re-used inics_auth.
- Important Dates
- Released to production October 7, 2024.
RM-30708
- Description
- To increase your safety and security, eCheck merchants who want to edit the bank account number that we have on file for them are required to provide a one-time password using email or SMS message.
- Audience
- U.S. merchants who use eCheck on the Visa Acceptance Platform.
- Benefit
- Additional security for your bank account.
- Technical Details
- None.
- Important Dates
- Released to production October 8, 2024.
RM-31470
- Description
- The one-time password (OTP) that we send when you log into the Sandbox (testing) Business Center now identifies the environment as Sandbox. For example,Cybersource Identification Code is 12346578 forOTP emails for the production version of the Business Center are not changed.sandbox. It will expire in 10 mins. DO NOT share it with anyone. We will never ask you for the code."
- Audience
- Users of the Sandbox (testing) Business Center.
- Benefit
- Now when you receive the OTP email, you can identify which environment it is for.
- Technical Details
- None.
- Important Dates
- Released to production October 11, 2024.