Skip to main content
Welcome to the preview portal — This is an early release of the new Doc Hub experience, with more content coming soon.

June 2026


Production releases for the weeks ending June 5 to June 26, 2026: features, fixed issues, and known issues.

June 26, 2026

These release notes cover releases for the week ending June 26, 2026.

Oracle NetSuite v26.3.0

Description: This release introduces PayPal v2 and Venmo as new payment options, adds JWT Header support for requests to strengthen API authentication, and enhances Payment Facilitator processing with card-brand-based Aggregator IDs for accurate transaction routing. Additionally, server-side scripting support has been added for the creation of Pay-by-Link invoices and pro-forma invoices, enabling automated invoice generation workflows. Follow-on refund requests for payment details have also been cleaned up, improving overall refund processing reliability and data consistency.

Mandate: Does not apply.

Audience: Users of Oracle NetSuite.

Benefit: This release introduces several enhancements to expand payment method coverage, strengthen authentication, and improve automation capabilities within the Payment Gateway integration for NetSuite. The updates ensure broader digital wallet support, modernized security standards, and greater flexibility for payment facilitator and invoicing workflows.

Technical Details: None.

Important Dates: Released to production June 17, 2026.


Oracle NetSuite v26.3.1

Description: This patch reverts the authentication method back to HTTP Signature due to an error with HTTP JWT. JWT will be re-introduced later.

Mandate: Does not apply.

Audience: Users of Oracle NetSuite.

Benefit: More reliable authentication.

Technical Details: None.

Important Dates: Released to production June 19, 2026.

No customer-facing fixes were released this week.

There are no known issues this week.

June 18, 2026

These release notes cover releases for the week ending June 18, 2026.

REST API

Ticket: RM-45368

Description: The Merchant Country of Origin feature adds a field to transaction messages that identifies the country where a merchant is legally registered, independent of where the transaction occurs. It is primarily required for government-controlled merchants when their country of origin differs from the acquiring or processing country, ensuring accurate representation in authorization and clearing.

Mandate: Mastercard mandate AN 8026.

Audience: Merchants who use these merchant category codes:

  • 9211 (Court costs including alimony and child support)
  • 9222 (Fines)
  • 9311 (Tax payments)
  • 9399 (Government services - not elsewhere classified)
  • 9402 (Postal services - government only)
  • 9405 (Intra-government purchases-government only)
  • 9406 (Government-owned lottery; global, excluding U.S. region)

Benefits:

  • Improves compliance with card network mandates
  • Supports issuer decisioning, monitoring, and regulatory controls
  • Helps prevent fines

Technical Details: Merchants should provide their valid country code in the merchantInformation.merchantDescriptor.countryOfOrigin field.

Important Dates: Released to production June 18, 2026.

No customer-facing fixes were released this week.

Invoicing

Ticket: EPS-38316

Description: A bug is causing the invoice tax amount to be overridden with a value of 0 for digital wallet payments.

Audience: Merchants using Invoicing with digital wallet payments enabled.

Technical Details: None.

Workaround: None.


Partner Risk Controls

Ticket: EPS-38325

Description: When a portfolio's subordinate account moves a merchant ID to a different risk profile in the Partner Risk Control feature in the , the change might take longer than expected to take effect. In some cases, it can take up to 24 hours, resulting in transactions continuing to be processed under the previous risk profile even after reassignment.

Audience: Acquirers.

Technical Details: None.

Workaround: None.


Decision Manager

Ticket: EPS-38386

Description: Sometimes Case Management's Summary view displays some merchant-defined data fields as string-encoded data instead of plain text. However, in Case Details, the fields appear correctly in plain text.

Audience: Owners of single portfolios.

Technical Details: None.

Workaround: None.

June 12, 2026

These release notes cover releases for the week ending June 12, 2026.

No customer-facing features were released this week.

Merchant-Initiated Transactions

Ticket: RM-46054

Description: assigns ISO Field 60 based on certain merchant parameters. Until now, subfield 60.8 has had a value of 02 for global recurring transactions, however, 02 applies only for U.S. and Canada. 07 is now supported for the rest of the world.

Audience: All acquirers and merchants who process recurring merchant-initiated transactions outside the U.S. and Canada.

Technical Details: None.

Important Dates: Released to Production June 12, 2026.

Virtual Terminal

Ticket: EPS-37322

Description: In the Virtual Terminal, when the ZIP/Postal Code is set as Required, the field appears in the One-Time Payment page, however, the requirement is not enforced for countries other than the U.S. and Canada.

Audience: Merchants outside the U.S. and Canada who use the Virtual Terminal.

Technical Details: None.

Workaround: None.


Fraud Management Essentials

Ticket: EPS-37175

Description: Exporting the Rule Performance Report generates incorrect values, causing numeric fields to appear duplicated. For example, a field that contains 123 is exported as 123123.

Audience: Users of Fraud Management Essentials.

Technical Details: None.

Workaround: None.


Credit Authorizations

Ticket: EPS-37776

Description: When a Credit Authorization is submitted using the REST APIs /credit endpoint and the authorization fails, the submitTimeUtc field is not returned.

Audience: Users of the REST API.

Technical Details: None.

Workaround: None.


Voids

Ticket: EPS-37884

Description: When a merchant in India attempts to void a transaction in the , an error message appears that says: Request failed due to system error, even in cases where the void was successful.

Audience: Merchants in India.

Technical Details: None.

Workaround: None.


Payments through TSYS

Ticket: EPS-37988

Description: A bug is triggered when a merchant submits a request for a combined authorization and capture transaction that includes the ignore_bad_cv field with a value of yes. If the authorization part of the transaction is hard-declined (Reason Code 203), the transaction is captured. This is incorrect because the transaction should be captured only for a soft-decline (Reason Code 230).

Audience: Merchants who process transactions through TSYS Acquiring Solutions.

Technical Details: None.

Workaround: None.


Partner Risk Controls (PaRC)

Ticket: EPS-38258

Description: PaRC users are unable to remove MIDs (merchant accounts) from PaRC profiles.

Audience: Merchants in Central Europe, the Middle East, and Africa.

Technical Details: None.

Workaround: Create a temporary profile, set the temporary profile to default, and then delete the temporary profile. This removes the default tag from the current profile, which fixes the problem.

June 5, 2026

These release notes cover releases for the week ending June 5, 2026.

Account Funding Transactions (AFTs)

Ticket: RM-45825

Description: Mastercard AFTs are now available on First Data Merchant Solutions (Europe) on OmniPay Direct and Lloyds TSB Cardnet International.

Mandate: Does not apply.

Audience: Merchants who use First Data Merchant Solutions (Europe) on OmniPay Direct or Lloyds TSB Cardnet International.

Benefit: Account Funding Transactions (AFTs) are used by merchants to withdraw funds from a senders account to fund a recipient account. For example, transferring funds between accounts or adding funds to a wallet or card.

Technical Details: Merchants must contact their Omnipay acquirer to ensure correct Merchant Category Code setup and registration for AFTs.

AFT transactions are indicated to Visa through presence of valid aftIndicator and businessApplicationID fields and sender and recipient payment details in the authorization and clearing messages.

For more information, see Mastercard AFT Developer Guidance for Omnipay Processing Connections.

Important Dates: Released to production June 4, 2026.


Merchant Advice Codes

Ticket: RM-45441

Description: is adding support for Merchant Advice Codes (MAC) in the Cielo3 authorization response flow. When Cielo3 returns a Merchant Advice Code on an authorization response, will pass that value through to the merchant in the existing merchant advice response fields.

Merchants will see this in the authorization response (API only, not in the ) for Cielo3 authorizations. The MAC value provides guidance on how to handle declined transactions, including whether to retry, when to retry, whether updated account information is available, or whether the customer should use another payment method.

The MAC value is informational only. It does not change the authorization decision, response code, reason code, or transaction status. Merchants do not need to change their authorization request and no additional boarding or enablement is required.

Prerequisites

  • The merchant is enabled for Cielo3 processing
  • The transaction is a supported Cielo3 authorization transaction
  • A Merchant Advice Code is available in the authorization response
  • The merchant uses a supported API response channel: REST or Simple Order API

Mandate: Does not apply.

Audience: Merchants processing through the Cielo3 processor in Brazil for authorization transactions.

Benefit:

  • Improved retry handling
  • Reduced unnecessary authorization attempts
  • Better customer-facing decline messaging
  • Improved recurring and subscription billing logic
  • Reduced support volume related to repeated declines

Technical Details:

Field Names

APICode FieldRaw Code Field
RESTprocessorInformation.merchantAdvice.codeprocessorInformation.merchantAdvice.codeRaw
Simple Order APIccAuthReply_merchantAdviceCodeccAuthReply_merchantAdviceCodeRaw

Supported Values

The MAC value is handled as a string and might be alphanumeric. Values up to four characters are supported. MAC values are not limited to a fixed list, and additional values might be returned over time.

Common MAC values include:

CodeDescriptionRecommended Action
01New account information availableUpdate account data where available
02Cannot be approved at this timeRetry after 72 hours or use another payment method
03Retry is not allowedDo not retry; request another payment method
04Token requirement is not metReview token requirements
21Plan cancelledStop billing attempts for the cancelled plan
24Try again after 1 hourRetry after 1 hour
25Try again after 24 hoursRetry after 24 hours
26Try again after 2 daysRetry after 2 days
27Try again after 4 daysRetry after 4 days
28Try again after 6 daysRetry after 6 days
29Try again after 8 daysRetry after 8 days
30Try again after 10 daysRetry after 10 days
40Retry is not allowedDo not retry; use another payment method
41Retry is not allowedDo not retry using the same single-use virtual card
43Multi-use virtual card guidanceAsk customer to generate a new virtual card or contact issuer

Example REST Response Snippet

"processorInformation": {  "merchantAdvice": {    "code": "03",    "codeRaw": "03"  }}

Important Dates: Released to production June 3, 2026.


Error Codes

Ticket: RM-45803

Description: Some REST API transactions that combine payment services with risk services incorrectly return the error 502 General System Error instead of 201 Decline.

Mandate: Does not apply.

Audience: Merchants who use the REST API.

Benefit: Correct error message.

Technical Details: None.

Important Dates: Released to production June 4, 2026.

Transaction Response Status

Ticket: RM-45638

Description: This release fixes an issue that cause bundled authorization and capture which were successfully authorized transactions to return the status PENDING instead of AUTHORIZED.

Audience: Merchants who use Payments 2.0.

Technical Details: Any change that was made to a merchant's system as a workaround for the incorrect status must now be restored to its original functionality.

Important Dates: Released to production June 2, 2026.

Decision Manager

Ticket: EPS-37196

Description: In Case Management, when a user exports a quick search to XML, an invalid XML attribute is generated in the downloaded file. This prevents the user from opening the exported file, leading to a validation error.

Audience: Users of Case Management in Decision Manager.

Technical Details: None.

Workaround: Replace the forward slash (/) within a SearchType/QuickSearch attribute name with a hyphen (-) or an underscore (_).


Invoicing and Portfolios

Ticket: EPS-37204

Description: When a portfolio account looks up the address of a child account, the address is sometimes different from the one listed in the child account.

Audience: Portfolio users of Invoicing.

Technical Details: None.

Workaround: None.


Transaction Details for Portfolio Accounts

Ticket: EPS-37405

Description: When portfolio users in the navigate from Manage Merchants to Transaction Details and then clicks the back button, they are redirected to the login page instead of Manage Merchants.

Audience: Portfolio users.

Technical Details: None.

Workaround: Perform the transaction search again without using the back button.


Transaction Search for Portfolio Accounts

Ticket: EPS-37429

Description: After new transacting organizations are created, users of merchant-level accounts might not be able to see transactions for those organizations immediately. In some cases, it can take up to a few weeks before the transactions become searchable.

Audience: Portfolio users.

Technical Details: None.

Workaround: Search for the transactions using a transacting or portfolio organization's user account instead of a merchant organization.


Decision Manager

Ticket: EPS-37478

Description: Merchants who use Account Takeover Protection in the see a red banner error when attempting to Mark as Suspect an event.

Audience: Merchants who use Account Takeover Protection.

Technical Details: None.

Workaround: Manually or Programmatically add information to the negative list.


Merchant Boarding

Ticket: EPS-37750

Description: During merchant boarding, when Payer Authentication is configured for Cartes Bancaires cards, the field for Acquirer ID does not accept hyphen (-) or space ( ) characters. However, Cartes Bancaires does accept those values.

Audience: Users of merchant boarding.

Technical Details: None.

Workaround: Contact the Support team.

Last published: November 18, 2026

Not available for your audience

This page isn't available for your current audience selection.