11 posts tagged with "Nuvei"

API​

Changed​

• Status API: Exposes the acquirer reference number (ARN) via the field extraData["arn"] when it is available.
• Transaction API: Exposes the acquirer reference number (ARN) via the field extraData["arn"] when it is available.

Fixed​

• Transaction API: Fix an issue where missing wallet data fields (walletOwner, walletReferenceId, walletOwnerFirstName, walletOwnerLastName, walletOwnerCountryCode) could cause an error. These fields are now treated as not provided.
• Transaction API: Implement stricter currency format validation, requiring merchants to send amounts with the correct number of decimal places for each currency (e.g., EUR: 9.99 or 9.9, JPY: 5 or 5.00). If the correct format can't be provided by merchants, the tenant can be configured to round amounts commercially according to our currency definition. These settings are inherited by sub-tenants. For assistance in configuring this setting, please contact your customer success manager.

Features​

Added​

• BI Data Source: Add a new data field, sub_type, for transaction subtypes related to rapid dispute resolution (RDR) in the BI data source.
• Login: Store redirect data in the URL to ensure that after multi-tab logout and login, each tab returns to the originally requested page instead of the landing page.
• Token Count Aggregation: Add filters to the post-processing step Calculate Token Count, allowing users to:
  1. Exclude Merchants having this Job Types scheduled
  2. Exclude Connectors having this Job Types scheduled
  3. Only Methods.

Fixed​

• Connector Configuration: Fix a bug in the transaction expiration process to ensure the Ignore Global Setting connector setting is respected whenExpire Pending Transactions or Expire Transactions is enabled.
• Connector Configuration: Fix an issue where a valid value of 0 for the connector setting Postback Queue: Set maximum number of retries was incorrectly treated as missing or invalid. The system now properly accepts 0 as a valid input.
• Documentation: Fixes the API authentication examples by removing the newline character that was incorrectly included in the base64-encoded concatenation of the username and password.

Adapters​

Changed​

• 2C2P (2C2P-EP1-2C2PB): Update the payment channels by removing Thanachart Bank and adding the new TMBThanachart Bank following the merger with TMB Bank.
• KCP Mobile, KCP PC (KCPMO, KCPPC): Add support for settlement handling.
• Mercado Pago (MERPA-PROD): Adds a new header to the payment request containing the DeviceData. This allows the collection of the DeviceID when redirecting the user to the Hosted Payment Page (HPP).
• PXP (PXP-EP1-CC): Map the field ProviderExternalID to acquirer reference number (ARN).
• Stripe (STRV2-EP1-CC, STRV2-EP3-CC (extends STRV2-EP1-CC)): Add the ability to pass requestExtendedAuthorization as extra data to Stripe to request an authorization to be extended for up to 30 days.
• Worldpay (WOR-EP1): Update AFT documentation.

Added​

• KakaoPay (KAKAO): Add the KakaoPay adapter with support for debit, refund and partial refund transactions. KakaoPpay is a South Korean fintech company specializing in digital payments, money transfers, and financial services.

Fixed​

• KCP Mobile (KCPMO-EP1):
  • Use Code as fallback response code if res_cd isn't available.
  • Fix an issue where the wrong value (payment method ID instead of payment method name) was sent for the pay_method field.
• Nuvei (NUV-EP1-CC): Fixes the fail-over transaction to Nuvei by ensuring that the firstPaymentDoTransactionId is only set if the related transaction was created through Nuvei; otherwise, it is omitted to prevent rejected transactions.
• PXP (PXP-EP1-INST): Fix wrong format of expiryMonth and expiryYear in adapter result.
• Zona Virtual SA - Zonapagos (ZONA-EP1): Fix status retrieval handling to consider only the latest status, as recommended by the PSP.

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.

Features​

Changed​

• BI Data Source: As announced, switch the BI Data Source endpoint /query/transactions from ElasticSearch to OpenSearch.

Fixed​

• API Testing: Replace username and password input fields with a user selector to reduce transmission of sensitive data.
• Customer Profile: Prevent the deletion of a customer profile’s payment instrument when deregistering a network token or PAN, even if the other was still present.
• Documentation: Update BI data source sandbox links in documentation to refer to sandboxbds.ixopay.com instead of sandbox.ixopay.com.
• Meta connector: Fix saving a routing rule node with an invalid ID or non-matching meta connector to show a proper error message instead of causing an internal error.
• Virtual Terminal: Fix internal server error in virtual terminal requests by verifying transaction object support before setting surcharge amount.

Adapters​

Changed​

• Alignet (ALI): Add support for settlement handling.
• dLocal (DLO-EP1-VPAY): Added support for the VPay QR payment method, enabling QR payments in Bolivia.
• EBANX (EBA): Add Endpoint connector configuration option to switch between Cross-border Endpoint and Local2Local (Domestic) Endpoint, with cross-border endpoint as the default.
• Nuvei (NUV):
  • Extend settlement handler to parse the new Settlement Summary Report Drill report type, selectable via the fileType field in the settlement data fetcher. Default remains Transaction Report.
  • Add automatic SFTP connection testing to settlement data fetchers.
• Payabl (P21-EP1): Update the testing endpoint to sandbox.payabl.com from sandbox.powercash21.com.
• Stripe (STRV2-EP1-CC, STRV2-EP3-CC): Add support for incremental authorization transactions for the Stripe adapter.
• Worldline (ING-EP2): Add shouldBeFinishedWhenCapturedTrustly connector setting to allow Trustly debit transactions to be marked as successful upon CAPTURED status, enabling customers to treat these transactions as finished.
• Worldline (ING-EP5): Forward transaction UUID as references.merchantReference in refund and capture requests.
• Worldpay (WOR-EP1): Add documentation for Account Funding Transactions (AFT).

Added​

• KCP Mobile (KCPMO-EP1): Add the KCP Mobile adapter with support for credit card and bank transfer payment methods. KCP Payment Solutions: Secure payment processing supporting multiple currencies and countries.
• KCP PC (KCPPC-EP01): Add the KCP PC adapter with support for credit card and bank transfer payment methods. KCP Payment Solutions: Secure payment processing supporting multiple currencies and countries.

Fixed​

• Worldline (ING-EP5): Fix a bug regarding the handling of webhooks.

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.

Features​

Added​

• Audit Log: A color-coded diff of the changes to a post-processing job's configuration is now available.

Fixed​

• Multi-method connector: Fixed the status poll for multi-method connectors and added a new connector setting (Delay autoCapture for debits by 5min) that can be used to delay the automatic capture.
• Network Tokenization: Fixed an issue that displayed disabled merchants in the NTS enrollment and Assign TRID drop-down lists.
• Post Processing Jobs: Fixed an issue with exporting data that would cause credit card data (e.g. the brand) to be empty in the exported file.
• Provider Settlements and Reconciliation: Fixed an issue with chargeback reversals that prevented them from being processed.
• UI Navigation: The network token status tab is now hidden if no network token is available.
• UI Navigation: Fixed an issue with sorting merchants and customer profiles.
• Virtual Terminal: Fixed an issue with the formatting of surcharge amounts when entered as a percentage instead of an absolute value.

Adapters​

Changed​

• Alignet (ALI-EP01-CC): Removed the merchant transaction ID section.
• checkout.com (CHE-EP1-CC):
  • Added billing post code/ZIP and billing state fields for AFT transactions.
  • When the Postback/Status: Include Auth-Code in postback/response and status response connector setting is enabled, the auth-code sent by Checkout.com is now included in the callback.
• Cybersource (CYS-EP1-CC):
  • Added support for partial capture
  • Mapped additional fields in API calls
  • Added support for the JapanPaymentOptions parameter for installments.
• DPO Pay (PAYGA-PYGT): Added support for handling callbacks.
• Nuvei (NUV): Added the ability to parse line items containing fees in settlement files.
• PXP (PXP): An SFTP host can now be defined for the settlement data fetcher. If no SFTP host is specified, the default host (sft1.servebase.net) is used instead.
• Zona Virtual SA - Zonapagos (ZONA-EP1): Added a setting to enable custom URLs for endpoints.

Added​

• China UMS (UMS): China UnionPay Merchant Services (China UMS) is a subsidiary of China UnionPay, a major financial services corporation in China. The adapter supports payments via Alipay and WeChat Pay.

Fixed​

• Adyen (ADY-EP3): Fixed an issue with the handling of the PresentToShopper result codes with the Multibanco payment method. The transaction is now set to pending instead of causing an error. This applies to all initial transaction types (debit, preauthorize and register).
• Alignet (ALI-EP01-CC): Fixed an issue with ID duplicates caused by simultaneous transactions.
• Alipay - Ant Group (ANT-EP1-ALIPL): Fixed a rare issue where an empty response would result in an error.
• American Express (AMX):
  • Transactions in American Express settlements can now also be resolved using the additionalId1 field. The settlement handler first checks the UUID and then the additionalId1 field.
  • Refund amounts are now saved as absolute values.
• checkout.com (CHE-EP1): Fixed an issue when mapping errors where the error code is empty.
• checkout.com (CHE-EP1-IDE, CHE-EP2-IDE): Improved the adapter's error handling.
• Mashreq (MASH): Debit calls include both a preauthorize and capture call. A 5 minute delay has been added to the capture due to recurring issues with instant captures.
• Mashreq (MASH-EP01): Fixed an issue with parsing the API response that could result in an invalid value, leading to an error.
• Worldline (ING-EP2): Fixed an issue with the data type used for the mandateDate.

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.

API​

Fixed​

• Transaction API: Fixed an issue where adapter error codes (errors.adapterCode) were sometimes returned as a numeric value instead of as a string.

Features​

Changed​

• Connector Configuration: When adding a connector or meta-connector, the public integration key is now prefilled with a random valid value. This value can still be edited and realtime feedback is provided on whether the edited value is valid.
• Connector Settings: Ensured referenceUuid is present in all cases when the connector setting Postback/Status: include reference uuid for all subsequent transactions in postback request and status response is enabled.
• Virtual Terminal: The virtual terminal has been reworked, including the Transaction, Customer, Credit Card and Payment details sections. New permissions have been introduced to handle the new streamlined form. Some of the business logic has been reworked or extended and GST calculations are now included in the Transaction section. The type of transactions available in the virtual terminal can now also be restricted using a new tenant/connector setting. For more information, refer to the User Manual.

Added​

• Connector Settings: Added a new connector setting Postback/Status: Include captureId for debit transactions in postback request and status response if available to enable sending captureId in callback requests and status responses.

Fixed​

• BI Data Source: Fixed the recurring status for chargeback and chargeback reversal transactions in the BI data source.
• Post Processing Jobs: Fixed an issue that would cause an error if the ID for a post processing job schedule was incorrect.
• Post Processing Jobs: It is now possible to add static values to aggregated lines in CSV exports by defining a default value for the static column field.
• Provider Settlements and Reconciliation: Settlements can now be resolved using all available IDs.
• Provider Settlements and Reconciliation: When assigning a connector to a provider, it is now possible to view and select the connectors for these merchants assigned to sub-tenants.
• User Management: Fixed an issue that could result in an error when a user attempts to change their password. In such cases, users are now redirected to the login page instead.

Adapters​

Changed​

• Adyen (ADY-EP1-CC, ADY-EP3-CC): Added support for network tokenization.
• dLocal (DLO-EP1): Added an option to omit the callback_url parameter, as this removes the back button on the dLocal payment page.
• Stripe (STRV2-EP1-CC): 3DS result data from Stripe is now included in callbacks.
• Worldpay (WOR-EP1): Added a new setting, Debit waits for webhook, to postpone marking a debit transaction as successful. This setting waits for the capture event webhook notification instead of relying solely on the authorization webhook.

Added​

• Worldline (ING-EP2-MUB): Added support for the Multibanco payment method (bank transfer). Multibanco is the largest interbank network in Portugal.

Fixed​

• Adyen (ADY-EP3): Updated the API documentation to include the merchantOrderReference parameter.
• Braintree (BRA): Added support for settling chargeback reversals.
• DPO Pay (PAYGA-PYGT-CC): Updated the adapter documentation to cover new capabilities (PreAuth, Void, Capture).
• E-Comprocessing, eMerchantPay (ECP-EP1, EME-EP3-CC): Added API documentation for eMerchantPay and E-Comprocessing.
• MultiSafepay (MUL-EP1): Fixed a typo in the status used by callback handling for chargebacks.
• Nuvei (NUV-EP1): Updated the API documentation to include information on mandatory fields.
• Nuvei (NUV-EP1-CC): Fixed an issue that caused the transaction ID to be incorrectly set to IXOPAY's internal UUID until the callback is received.

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.

API​

Fixed​

• Batch Upload API: Fixed a number of issues with the Batch Upload API:
  • Fixed a bug that generated an incorrect output format when an error occurred.
  • Fixed an issue when querying the status of a batch request that would result in an HTML response being generated when the batch ID referenced a non-existent batch. A JSON response is now generated containing "batch not found".
  • In cases where validation errors (e.g. the merchantTransactionId is already assigned) prevents a transaction from being created, the transaction was not written to the output at all. The output now includes a line with success = false, along with an error message in the output file for every transaction that could not be created.
• Transaction API: Removed the thousands separator from the amount field in callbacks for transactions with a surcharge fee.

Features​

Changed​

• UI: The Tools section in the platform has been overhauled. The entries previously located here have been moved to more relevant parts of the platform - this includes options such as BitPay pairing and Tokenization.

Added​

• Job Configuration: Added a new feature to automatically add comments to potentially fraudulent transactions and send out emails with relevant information.

Fixed​

• Connector Settings: Fixed a minor visual issue that occurred when selecting the same connector setting twice. The setting was then displayed twice. The setting is now only displayed once.
• Post Processing Setting: Fixed an issue with sending callbacks for transactions created via settlements.
• Transaction List Filter: Fixed an issue with the filter for transactions created in test mode not being applied correctly.
• User Management: Fixed an issue where users were unable to add new merchant users unless they had the frontend.users.roles.edit permission.

Adapters​

Changed​

• Amazon Payment Services (AMAZO-EP1-CC): Added support for the new JSON settlement format.

Added​

• Alignet (ALI-EP01-CC): Alignet is a leading technology company based in Peru, specializing in solutions for secure electronic transactions. They pioneered the use of 3-D Secure in Latin America and are a key supplier of major banks in the region. The adapter supports credit card transactions.
• Braintree (BRA-EP1): Added support for the Blik payment method. Blik allows for bank transfers and covers all major Polish banks.
• PayTabs (PAYT-EP01-VALU): PayTabs is a payment processing solution specializing in seamless online transactions in areas such as the Middle East, North Africa and Southeast Asia. The adapter currently supports payments using the valU BNPL payment method in Egypt.
• Worldline (ING-EP2): Added a new endpoint as well as the option to switch between old and new endpoints in the configuration.
• Worldpay, checkout.com (CHE, WOR): Updated the API documentation for checkout.com and WorldPay WPG to include AVS and CVV responses.

Fixed​

• Adyen (ADY-EP3): Fixed an issue with missing notification verification for AdyenCheckout.
• Adyen (ADY-EP3-RIV):
  • Added support for partial captures for the Riverty payment method using Adyen Checkout.
  • The IP address field is now optional instead of mandatory when using the Riverty payment method with AdyenCheckout.
• Bitpay (BTP-EP1-CR): Fixed pairing issues with the new Bitpay connector configuration.
• Braintree (BRA-EP2): Fixed an issue with Braintree's Address Verification Service.
• checkout.com (CHE):
  • Fixed the handling of settlements for transactions with multiple partial captures.
  • Multiple fees are now supported for a single transaction in the settlement report.
• Klarna (KLW-EP1-APM): HTTP 400 responses are now mapped correctly.
• Mashreq (MASH-EP01): Added handling for the status "Awaited", which previously returned an error (due to this status not being documented by CCAvenue). The transaction is now set to pending when this status is received.
• MultiSafepay (MUL): Fixed an issue with the settlement fetcher that prevented settlements from being retrieved.
• Nuvei (NUV-EP2): Enabled support for partial captures.
• Zona Virtual SA - Zonapagos (ZONA-EP1):
  • A unique numeric value is now generated and sent to Zona Virtual as the payment ID Id_pago. This value is stored in the additionalId1 field in IXOPAY as a payment reference that is used if the payment fails.
  • Changes have been made to the mandatory fields. The following fields are no longer mandatory: merchantMetaData, extraData.idType, customer.identification.
  • Fixed the default error mapping.
  • Added mapping for the error when a payment cannot be found.

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.