17 posts tagged with "Nuvei"

Gateway Features​

Changed​

• Provider Settlements and Reconciliation: Rename Reconciliation Conflicts page to Provider Reconciliations.
• Risk Profile: Rename Cumulative Score column to Total Score.

Added​

• Connector Settings: Add a new connector setting Postback: Defer sending until after the API response has been returned.

Fixed​

• Transaction Processing: Fix an issue that could cause a Token not found error in certain circumstances.

Gateway Adapters​

Changed​

• dLocal (DLO-EP1-MP): Add support for the new payment method MultiPago. MultiPago is a cash-based payment method in Latin America that allows customers to pay for online purchases using payment slips at convenience stores or banks.
• Nuvei (NUV-EP1-ALIUN): Add support for the new payment method Alipay+ Unified Payment. Alipay+ Unified Payment is a cross-border digital payment solution that allows customers to pay with various supported e-wallets and other payment methods across multiple regions.
• Nuvei (NUV-EP1-RAKUT): Add support for RakutenPay, a Japanese e-wallet that lets customers pay online or in-store via the app or by scanning a QR code.
• PayPal Complete Payments - PPCP (PPCP): Add support for sending transaction context if data is provided.
• PayPal Complete Payments - PPCP (PPCP-EP1-PPE): Add a new setting useProvidedMerchantUrls to fix mobile payment processing for merchants using PayPal's iOS/Android SDK.

Fixed​

• Cybersource (CYS-EP1-CC): Fix mapping of transaction indicators to the commerceIndicator.
• JCC Payment Systems (JCC-EP1-CC): Fix mapping and handling of callback notifications.
• KakaoPay (KAKAO-EP1-KAKAO): Fix refund handling to ensure each refund is correctly matched and settled.
• Worldpay (WOR): Ensure correct behavior for debit transactions by setting delay capture to 0.

Please note that some of the features mentioned in the release notes may initially be available only within our sandbox environment for testing purposes. These features will be made available in the production environment upon successful testing and approval.

Gateway API​

Fixed​

• Provisioning API: Fix bug where an auto-generated shared secret on connector creation returned a value longer than the actual stored one.

Gateway Features​

Changed​

• Risk Profile: Update Forter risk engine to use Dispute API (v10.1).
• Risk Profile: Add configurable Forter risk engine 3DS recommendations with an option to adjust 3DS requirements for transactions based on those recommendations.

Added​

• Fee Management: Add new fee constraint 3DS (options: any or inhouse) which allows setting fees based on the 3DS environment used for a transaction.
• Fee Management: Improve the transactionSubType constraint by showing any as the default option.
• Transaction Details: Add viewing of fraud tags in the Transaction Details page for merchant users. Enable with the frontend.transaction.tag.show permission. Admin users have the transaction.tag.show permission enabled by default.
• Transaction List: Add the Advanced Filter with a simplified set of filter options for merchant users in the Transactions view. It can be enabled with the frontend.transaction.advanced-search permission.

Fixed​

• Risk Profile: Fix an edge case where transaction risk data couldn't be stored.

Gateway Adapters​

Changed​

• dLocal (DLO-EP1-VPAY): Enable V Pay for Paraguay.
• JPMorganChase (CHA):
  • Add new setting to select report type: Funded Transaction Fee Details (FTI) or Settlement Details (PE).
  • Add new setting to specify settlement retrieval type: Polling-Based Retrieval or Notification-Based Retrieval.
• Nuvei (NUV-EP1-PSE): Update documentation for payment method PSE.

Fixed​

• JPMorganChase (CHA): Fix several issues with notification handling and settlement file retrieval.
• MultiSafepay (MUL-EP1-CC): Attempt to retrieve the scheme reference identifier from the initial MultiSafePay transaction if it was missing in order to facilitate recurring transactions.

Please note that some of the features mentioned in the release notes may initially be available only within our sandbox environment for testing purposes. These features will be made available in the production environment upon successful testing and approval.

Gateway Features​

Changed​

• Meta connector: Remove the option to change the type of an existing meta-connector (routing / multi-method) to prevent unexpected behavior and ensure consistent functionality.

Added​

• Connector Settings: Add a new connector setting Add Hard Decline Error Codes which allows specifying additional error codes that prevent failover transactions.

Fixed​

• Connector Settings: The connector setting Accept postbacks from other connectors will now properly ignore meta-connectors if provided in the list.
• Provider Settlements and Reconciliation: Fix an issue where a transaction was not settled correctly if a fee-only settlement in a different currency was received before the actual transaction settlement.
• Transaction Processing: Transactions with an expired or non-existent transaction token will no longer be retried.
• User Management: Fix a minor display inconsistency in the permissions list when configuring roles.

Gateway Adapters​

Changed​

• Adyen (ADY-EP4-CC): Add additional data mappings and documentation.
• Amazon Payment Services (AMAZO): Add settlement handling.
• Amazon Payment Services (AMAZO-EP1-NAP,AMAZO-EP2-NAP): Add support for the new payment method NAPS. NAPS is Qatar's national debit card network which offers a convenient, card-independent local payment method, enabling seamless, real-time transactions between businesses and Qatari shoppers across participating Qatari banks.
• Bangkok Bank (BB): Adjust settlement handling to support a new VAT format with VAT provided once per file instead of per transaction.
• Nuvei (NUV-EP1-PSE): Add support for the new payment method PSE. PSE (Pagos Seguros en Línea) is a popular real-time online bank transfer payment method in Colombia that allows users to pay directly from their bank accounts.
• Worldpay (WOR-EP1-KLAPN): Use a default Order Line Item if none is provided, to meet mandatory requirements by Worldpay for Klarna.

Added​

• Digit Secure (DS-EP1-T2P): New push adapter with payment method Tap2Pay.

Fixed​

• Cybersource (CYS): Fix parameter typo from extraData.reconciliationId to extraData.reconciliationID (captialize D in ID).
• KakaoPay (KAKAO-EP1-KAKAO): Fix incorrect mapping of error responses.
• KCP Mobile (KCPMO): Fix issue with settlement handling for refund transactions.
• KCP PC (KCPPC): Fix issue with settlement handling for refund transactions.
• Simulator: Fix issue where payment.js did not work with the Simulator adapter.

Please note that some of the features mentioned in the release notes may initially be available only within our sandbox environment for testing purposes. These features will be made available in the production environment upon successful testing and approval.

Gateway API​

Fixed​

• Batch-upload API: Resolve a limitation that previously prevented the processing of batch files with more than ~50 transactions.

Gateway Features​

Changed​

• Transaction Details: Improve clarity for transaction fee names.
• Transaction Details: Allow manual chargebacks, second chargebacks, and chargeback reversals to be processed for an amount greater than the original transaction.

Added​

• Transaction Details: Add the option to use a custom merchant transaction ID for manual Voids and Refunds.

Fixed​

• Hosted Payment Pages: Fix possible race condition when loading JavaScript on the Hosted Payment Pages in certain scenarios.
• Provider Settlements and Reconciliation: Fix a minor bug in the settlement process when handling chargeback reason codes.

Gateway Adapters​

Changed​

• checkout.com (CHE): Minor improvements to reliability for callback handling.

Added​

• Amazon Payment Services (AMAZO-EP1-KNET, AMAZO-EP2-KNET): Amazon Payment Services is a leading payment provider in the Middle East, offering secure and localized payment solutions. The new adapter supports the payment method KNET for transaction types Debit and Refund. KNET is a popular debit-based payment network in Kuwait, enabling real-time bank transfers for online purchases.

Fixed​

• DPO Pay (PAYGA-PYGT-CC): Fix issue where transaction status was not properly retrieved after communication errors.
• Nuvei (NUV): Fix issue causing the reserve to be incorrectly saved as a transactional fee.
• Simulator: Fix a configuration issue for Simulator settlement handling.

Portal​

Changed​

• Proxy Tokenization (Deployed in release v25.9):
  • Support special characters in alias
    • Dash and underscore supported only
  • Bug fix - Profile details to display ID number if optional name is empty
  • Profile & Key name auto save
    • Auto save optional name upon click outside of field
  • Account Logging
    • Profile, Key & Alias event tracking
      • Create
      • Edit
      • Delete

Please note that some of the features mentioned in the release notes may initially be available only within our sandbox environment for testing purposes. These features will be made available in the production environment upon successful testing and approval.

Gateway API​

Fixed​

• Provisioning API: Fix an error that occurred when attempting to update merchant users with apiUserSettings configured.

Gateway Features​

Changed​

• Connector Configuration: Change save message of connector configuration to display multiple validation errors simultaneously, instead of just one.
• Risk Profile:
  • Applied cosmetic changes for consistency, including button renaming and layout adjustments.
  • Restricted Audit Log access with the Admin User Permission misc.show-public-audit-log.

Added​

• API Testing: Add a Clear CC Token button to the API Testing view to reset credit card fields without refreshing the page.
• Risk Profile: Add a new risk rule to validate the presence of both the transaction indicator and reference scheme ID.
• Risk Profile: Add support for BIN segments (Consumer, Business, Commercial, Government, Unknown) and add a new risk rule BIN segment of credit card is [in, not in] [list of segments] to replace the previous BIN level of credit card is [in, not in] [list of levels] rule in the future, allowing checks for specific BIN segments.

Fixed​

• Connector Settings: Fix compatibility of the Manipulation: Always set withRegister connector setting on meta-connectors with Customer Profiles to ensure payment instruments are properly stored.
• Provider Settlements and Reconciliation: Fix an issue where the upload button remained in the uploading state after a manual file upload error.

Gateway Adapters​

Changed​

• dLocal (DLO-EP1):
  • Add /options/installmentsPlan endpoint to retrieve installment plans.
  • Add extra data parameters to debit and preauthorize transactions to enable installements (extraData.installments and extraData.installments_plan_id).
  • Change required status of customer.nationalId from mandatory to optional.
• JPMorganChase (CHA-EP2): Add support for partial void transactions.
• KakaoPay (KAKAO-EP1): Add support for settlement and reconciliation handling.
• Nuvei (NUV-EP1):
  • Change required status of customer.email from mandatory to optional.
  • Change sFTP retrieval to no longer require permissions to rename the file on the remote server for settlement and reconciliation handling.
• PayPal Complete Payments - PPCP (PPCP-EP1): Add chargeback protection details to postback response, including seller protection status (extraData.seller_protection_status), dispute categories (extraData.seller_protection_dispute_categories), and PayPal account status (extraData.paypal_account_status).
• Worldpay (WOR-EP1): Add postback handling for online refunds. Merchants will receive the Refund Authorisation Reference number in extraData.refundAuthorisationReference via postback.

Added​

• Banco Popular Dominicano (BPD-EP1): Add the Banco Popular Dominicano adapter with support for debit transactions. Banco Popular Dominicano is the first privately owned bank in the Dominican Republic and is the leader in a wide range of banking and financial services in the country. It is the principal company of Grupo Popular.

Fixed​

• Global Payments (GBP): Prevent duplicate settlement errors by using more specific settlement batch numbers.
• JPMorganChase (CHA-EP2):
  • Fix handling of partial void followed by capture.
  • Update extraData.totalAuthAmount after partial void.
• PayPal Complete Payments - PPCP (PPCP-EP1-PPE):
  • Enable partial capture and void capabilities for the PayPal payment method via the PayPalCompletePlatform adapter.
  • Ensure that the PayPal Partner Attribution ID is set for transactions processed through multi-method connectors.
• PXP (PXP-EP1): Fix mapping of error code 100(77).
• Stripe (STRV2-EP1): Use net amount instead of gross amount when parsing Line Items and Rolling Reserve for the Stripe Settlement Report.

Please note that some of the features mentioned in the release notes may initially be available only within our sandbox environment for testing purposes. These features will be made available in the production environment upon successful testing and approval.