On This Page
Features Introduced This Week
Account Funding Transactions (AFTs) | RM-45825
Account Funding Transactions (AFTs)
| 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 in order 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 validaftIndicatorandbusinessApplicationIDfields and sender and recipient payment details in the authorization and clearing messages.
- For more information, seeMastercard AFT Developer Guidance for Omnipay Processing Connections.
- Important Dates
- Released to production June 4, 2026.
Merchant Advice Codes | RM-45441
Merchant Advice Codes
| RM-45441- Description
- Cybersource 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, Cybersource 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 Business Center) 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, SCMP, 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 FieldRESTprocessorInformation.merchantAdvice.codeprocessorInformation.merchantAdvice.codeRawSCMPauth_merchant_advice_codeauth_merchant_advice_code_rawSOAPIccAuthReply_merchantAdviceCodeccAuthReply_merchantAdviceCodeRaw
- Supported Values
- The MAC value is handled as a string and may be alphanumeric. Values up to four characters are supported. MAC values are not limited to a fixed list, and additional values may be returned over time.
- Common MAC values include:
- CodeDescriptionRecommended Action01New account information availableUpdate account data where available02Cannot be approved at this timeRetry after 72 hours or use another payment method03Retry is not allowedDo not retry; request another payment method04Token requirement is not metReview token requirements21Plan cancelledStop billing attempts for the cancelled plan24Try again after 1 hourRetry after 1 hour25Try again after 24 hoursRetry after 24 hours26Try again after 2 daysRetry after 2 days27Try again after 4 daysRetry after 4 days28Try again after 6 daysRetry after 6 days29Try again after 8 daysRetry after 8 days30Try again after 10 daysRetry after 10 days40Retry is not allowedDo not retry; use another payment method41Retry is not allowedDo not retry using the same single-use virtual card43Multi-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 | RM-45803
Error Codes
| RM-45803- Description
- Some REST API transactions that combine payment services with risk services incorrectly return the error502 General System Errorinstead of201 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.