RM-26348
  • Description:
     the Barclays gateway has been updated to support marketplace merchants identifying a transaction where the sub-merchant is a foreign entity.
  • Audience:
     merchants using Barclays2 gateway.
  • Benefit:
     Visa mandates flagging such transactions, so merchants will be able to correctly submit their marketplace transactions.
  • Technical Details:
     on a settlement message, add the following API field, where the value is an ISO 3166-1 country code:
    • REST API
      :
      aggregatorInformation.subMerchant.country
    • Simple Order API
      :
      invoiceHeader_submerchantCountry
    • SCMP API
      :
      submerchant_country
      If the merchant country is not submitted in the API request, the value configured for the merchant account during onboarding will be used instead. The value submitted in the API request supersedes any value configured for the merchant account.
      Your Cybersource merchant configuration should also have a merchant country set as the marketplace's operating country. If this is not supplied, or you wish to override the Merchant Configuration value, supply a ISO 3166-1 country code in the following request field:
    • REST API
      :
      merchantInformation.merchantDescriptor.country
    • Simple Order API
      :
      invoiceHeader_merchantDescriptorCountry
    • SCMP API
      :
      merchant_descriptor_country
  • Important Dates:
     released to Production on January 30, 2024.
RM-26348
  • Description:
     this release enables support for Card on File Network Tokenisation transactions.
  • Audience:
     merchants that use the following gateways:
    • Barclays
    • Global Payments International Acquiring (OmniPay Direct)
    • Cardnet International (OPD Cardnet)
    • FDMS Europe (OPD FDE)
  • Benefit:
     this update enables the processing of network tokens generated by Card on File storage for the supported gateways. This will allow correct segregation of Network Token types for schemes.
  • Technical Details:
     in an authorization message, follow the existing guidelines for a Network Token Transaction, but set the value of the following field to 3 instead of 1:
    • REST API
      :
      paymentInformation.tokenizedCard.transactionType
    • Simple Order API
      :
      paymentNetworkToken_transactionType
    • SCMP API
      :
      payment_network_token_transaction_type
  • Important Dates:
     released to Production on January 30, 2024.
RM-23902
  • Description:
     Decision Manager documentation in the Business Center has been updated with a Training section.
  • Audience:
     Decision Manager documentation is only available for users of Decision Manager.
  • Benefit:
     merchants that use Decision Manager and can use the training to further increase their knowledge.
  • Technical Details:
     none.
  • Important Dates:
     released to Production on January 31, 2024.
RM-23902
  • Description:
     the Partner Risk Controls Dashboard (PaRC) in the Business Center has been enhanced so that Active Risk Controls now display merchants that have PaRC System Integrity Fees (SIF) enabled.
  • Audience:
     users of the Partner Risk Controls Dashboard.
  • Benefit:
     ability to filter merchants by SIF features.
  • Technical Details:
     none. No action needed.
  • Important Dates:
     released to Production on January 31, 2024.
RM-21919
  • Description:
     this release updates Transaction Search by adding a new parameter to the Application search filter in the Business Center and the API. The new parameter is Card Credit Authorization Reversal. This change is available in the Business Center Search Toolbar, the Search Results feature, and the Transaction Details Page. For API querying, see Technical Details.
  • Audience:
     users of Transaction Search.
  • Benefit:
     the ability to search for credit card authorization reversals.
  • Technical Details:
     to use the new search filter in an API request, use the query parameter and value of
    applicationInformation.applications.name
    :(ics_credit_auth_reversal)
    . For more information about API search using query parameters, see Filtering by Query Parameter.
  • Important Dates:
     released to Production on January 29, 2024.
RM-26514
  • Description:
     in this release, we added a new search value to our Transaction Search feature for both the Business Center and the API. In the Business Center's Transaction Search page, in the Payment Solution drop-down menu, you can now select Paze. Paze also appears in Transaction Details Page. For API querying, see Technical Details.
  • Audience:
     users of Transaction Search.
  • Benefit:
     the ability to search for transactions that use Paze.
  • Technical Details:
     to use the new search filter in an API request, use the query parameter and value of
    processingInformation.paymentSolution
    :029
    . For more information about API search using query parameters, see Filtering by Query Parameter.
  • Important Dates:
     released to Production on January 29, 2024.
RM-26772
  • Description:
     To comply with a mandate from the Reserve Bank of India, merchants in India will not be able to search for transactions beyond 6 months. Saved searches which contained a 12 or 13-month date range are updated to 6 months.
  • Audience:
     merchants in India.
  • Benefit:
     compliance with a mandate from the Reserve Bank of India.
  • Technical Details:
     none.
  • Important Dates:
     released to Production on January 29, 2024.