Features Introduced This Week {#rn-features} ============================================ **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 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*](https://developer.cybersource.com/docs/cybs/en-us/payouts/developer/opdfde/rest/payouts-dev/payouts-services-intro/payouts-services-auth-aft-intro-opd-mc.md ""). Important Dates : Released to production June 4, 2026. **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 {#rn-features_ul_jjs_q5f_mjc} 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 {#rn-features_ul_jgj_l5f_mjc} Technical Details : **Field Names** : |---------|------------------------------------------|---------------------------------------------| | **API** | **Code Field** | **Raw Code Field** | | REST | processorInformation.merchantAdvice.code | processorInformation.merchantAdvice.codeRaw | | SCMP | auth_merchant_advice_code | auth_merchant_advice_code_raw | | SOAPI | ccAuthReply_merchantAdviceCode | ccAuthReply_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: : |----------|-----------------------------------|---------------------------------------------------------------| | **Code** | **Description** | **Recommended Action** | | 01 | New account information available | Update account data where available | | 02 | Cannot be approved at this time | Retry after 72 hours or use another payment method | | 03 | Retry is not allowed | Do not retry; request another payment method | | 04 | Token requirement is not met | Review token requirements | | 21 | Plan cancelled | Stop billing attempts for the cancelled plan | | 24 | Try again after 1 hour | Retry after 1 hour | | 25 | Try again after 24 hours | Retry after 24 hours | | 26 | Try again after 2 days | Retry after 2 days | | 27 | Try again after 4 days | Retry after 4 days | | 28 | Try again after 6 days | Retry after 6 days | | 29 | Try again after 8 days | Retry after 8 days | | 30 | Try again after 10 days | Retry after 10 days | | 40 | Retry is not allowed | Do not retry; use another payment method | | 41 | Retry is not allowed | Do not retry using the same single-use virtual card | | 43 | Multi-use virtual card guidance | Ask 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 --------------------------- 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.