This changelog covers changes to the documentation and API Reference during March 2024.

Content changes

• Added a conceptual page about creating a product page that shows local currency and prices that links to the existing Recipe and also provides more insights on options for implementing multi-currency pricing (MCP). (3/20/2024)
• Added the PayU Asia Pacific (via PaymentsOS) integration guide so you know how to work with this Connection. (3/13/2024)
• Updated the paymentType documentation and reference table because of updates with Mastercard's compliance requirements, which will be in effect soon. To ensure that these changes have minimal impact on you, please review the following key points:
  • Compliance Requirement: Mastercard now requires detailed info on payment types (like Merchant Initiated Transactions, Customer Initiated Transactions, recurring payments, and so forth) to be sent through payment platforms. These steps are crucial for keeping payment processing secure and transparent.
  • Compliance Deadline: The deadline for compliance is May 31st. It is possible for fines to be assessed if there are transactions being sent incorrectly. You can find details on the required data, as well as potential fines for non-compliance, in Mastercard's compliance documentation (if you need this documentation, contact Integrations Support).
  • Handling Default Values: For MIT/CIT and recurring transactions, our API can capture the needed data with the paymentType field. If you're already using this field, you're all set for the first part of the compliance. If not, we'll use default values based on the transaction's workflow and metadata. For accuracy and compliance, you may need to set the paymentType in some cases. The paymentType documentation has all the details, and we're here to help with any changes you might need to make.
  • Initial Transaction References for MITs: Mastercard also wants a reference to the first customer-initiated transaction for subsequent merchant-initiated ones. Often, this info is automatically included when processed through Nexio. In some situations, we'll use a static value to meet this requirement. We're actively working on the few exceptions to this rule and will reach out if to merchants if their transactions are affected, ensuring everything runs smoothly.
  • Need Assistance?: If you have any questions or need help, please contact our integration support team.
    We understand that these updates may require some adjustments on your part, and we appreciate your prompt attention to this matter. Nexio is here to support you through these changes to ensure a smooth transition and continued compliance with Mastercard's requirements.
    We also updated content in several other tutorials because of this change: Creating a card checkout page with the iframe, Creating a card checkout page with your own form, Running a card transaction with the API, Running a card transaction using full card information, Customizing the retail iframe, Creating a Nexio-scheduled card subscription, Running merchant-initiated transactions for a subscription, Setting up installments for a bank to handle the subscription, Creating a Nexio-scheduled card payment plan, Running merchant-initiated transactions for a payment plan, Creating a Nexio-scheduled card payment plan
    (3/13/2024)

API changelog

If you have any questions or feedback, contact us.