Skip to main content

7 posts tagged with "DPO Pay"

View All Tags

v.24.3

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 Settlement: 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.

v.24.2

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: Settlements can now be resolved using all available IDs.
  • Provider Settlements: 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.

v.23.21

Features

Fixed

  • Transaction Details: Additional headers for callbacks including Content-Type, Accept and User-Agent are now added to the postback transaction logs in the transaction details view when the postback:send-test-plain-header or postback:send-useragent-header are set in the connector settings.
  • Transaction Export: Fixed an issue with the export of transaction data for merchants with mult-merchant access.
  • UI Navigation: The Croatian and Slovenian translations have been updated.

Adapters

Changed

  • Braintree (BRA-EP2-CC): The connector configuration has been updated, see the documentation for more information.
  • Braintree (BRA-EP1): The additionalId1 field is now mapped to the descriptor name instead of the descriptor URL.
  • Cybersource (CYS-EP1-CC): Updated the description of auxiliary data in the documentation.
  • DPO Pay (PAYGA-PYGT): The DPO Pay adapter now supports preauthorize, capture and void transactions for credit cards.
  • Worldpay (WOR-EP1-CC): The API documentation has been updated to include information on which parameters are mandatory for the Worldpay WPG PCI adapter.

Fixed

  • ATOM (an NTT DATA Company) (ATOM-EP1-CC): Fixed an error with retrieving the settlement that was introduced in an earlier change.
  • Braintree (BRA): The createdAt timestamp supplied in Braintree's postback is now used as the timestamp for PayPal chargebacks.
  • DPO Pay (PAYGA): Fixed an issue that prevented settlements from being processed due to an invalid date format.
  • EPG Financial Services Limited (EPG-EP01-PAYLA): If the additionalId1 field is not provided as part of the payout request, the alias of the referenced debit transaction is used as a fallback option.
  • GoCardless (GOC-EP1): Fixed an issue with the server-to-server flow caused by a missing parameter.
  • Valitor (VALIT-EP1-CC): Fixed an issue with settlements caused by duplicate transaction lifecycle IDs.

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.

v.23.16

Features

Changed

  • 3DS: Rolled back changes that removed 3DS postback data for merchants using external MPI.
  • Transaction details: The payment token is now included in the customer profile data in callbacks and API status calls.

Added

  • Post Processing: The filter in the Collect All Transactions (in period) Post Processing collecting step now supports filtering adapter errors and internal errors by the date on which their status changed.
  • Provider settlements: Added a new tab to the conversion rate system settings that allows deviation tolerances to be defined for currency pairs per tenant. This is then used to verify settlements rather than the tenant's global tolerance or default tolerance (0.02%).
  • Settings: Added a new project setting, Postback: Include Basic Auth header, which allows a header to be sent for basic-auth postback. This setting is also available as a global connector setting.

Fixed

  • Account Updater: Fixed an issue where only one level of sub-tenants were filtered. Fixed an issue that would cause an error when changing the master tenant in the detailed view.
  • Customer profile: Fixed an issue that triggered an error when creating a customer profile via the API's customerProfileData field without setting any customer data in the transaction.
  • Pay-by-Link: Fixed an issue that would result in an empty redirect URL. Fixed an issue with redirects to expired pay-by-link transactions without an error URL that would cause an exception. The correct page is now displayed.
  • Pay-by-Link: Fixed an issue that caused all pay-by-link transactions to be withRegister transactions. It is now possible to choose whether the transaction should be a withRegister transaction or not using the with Register (Store Payment Instrument for Card-on-File payments) checkbox.
  • Post Processing: Fixed an issue that would cause an error for sub-tenants when attempting to select job configuration templates created at the parent provider level if no fee entities were available in the template.
  • Risk Engine: Fixed an issue with the Count of different credit cards of same device risk rule if no customer or browser data is available.

Adapters

Changed

  • checkout.com (CHE-EP1-CC): The AVS and CVV results are now added to the extraData in callbacks if available in the response.
  • DPO Pay (PAYGA-PYGT-PMR): Added support for the USSD payment method.
  • eMerchantPay (EME): Added support for chargeback reasons, which are now forwarded to merchants.
  • Nuvei (NUV): Updated the Westpac settlement handling.
  • Paysafecard (PSC): Added support for payouts.
  • Redsys (RED-EP2-BIZ): Added support for refund transactions.

Added

  • Nuvei (NUV-EP1-CC): Added support for chargeback notifications from Nuvei.

Removed

  • Bank of America (BOFA-EP1-ACH): The Addenda row was removed from the NACHA file when using the WEB format, as it is not required.

Fixed

  • Nuvei (NUV-EP1-CC): Fixed issues with the references to related transactions, which should either contain the Nuvei transaction ID, the transaction ID of the previous 3DS request, or the transaction ID of the authorized payment.
  • Nuvei (NUV): To handle issues with settlements, a new optional configuration setting has been added for the reconciliation data fetcher ID, which checks whether the system needs to wait for the CB report for the same date when retrieving settlements.
  • PPRO (PPR-EP1): Fixed an issue with settlements, that is caused by PPRO sometimes providing multiple files with the initial file only containing volume data, and subsequent files containing the actual transaction settlement data. A new option is now available in the data fetcher configuration, Only retrieve settlements if all fees and volume files are present that checks whether all settlement files are present before retrieving and processing the files.
  • Valitor (VALIT-EP1-CC): Fixed an issue related to duplicate transaction IDs issued by Valitor that would cause refunds to be ignored in settlements due to another transaction having the same ID.
  • Volt (VOL-EP1): Fixed an issue with Volt settlement files caused by the formatting of the CSV data.

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.

v.23.14

API

Fixed

  • Provisioning API: Fixed an issue with the Provisioning API that would prevent the creation of vault connectors under specific circumstances.

Features

Changed

  • Fee Engine: Changed the behavior for configuring GST fees to reflect the Surcharge dependencies.

Added

  • 3DS: The highest-supported 3DS version is now used where possible (i.e. 3DS v2.2.0 is used instead of v2.1.0). For more details, see 3DS 2.1.0 EOL and Changes to 3DS in IXOPAY.
  • Connector Settings: A new connector setting has been added (Postback/Status: Include isAFT in postback/status response) that includes information on whether AFT was performed using this transaction.
  • Post Processing: Added the ability to check whether data fetchers are set up correctly after adding or editing the data fetcher (currently only supported with the SepaExpress v1 settlement data fetcher). Results are shown in the data fetcher edit view.
  • Risk Profile: Added a filter check for all transactions with a payment instrument where the doNotResubmit flag is set for the Count of transactions using same payment instrument risk rule. Added the transaction's error status (error_adapter, error_internal, cancelled, invalid) to the transaction's status selection for the Count of transactions using same payment instrument risk rule.
  • Translation: Added Croatian and Slovenian to the merchant admin interface.

Fixed

  • 3DS: When external 3DS solutions are used, the values are no longer included in the postback, as IXOPAY can neither guarantee they are correct nor complete.
  • Customer profiles: Fixed an issue that resulted in an incorrect wallet reference ID being entered in customer profiles.
  • Multi-method connector: Fixed an issue relating to the retrieval of customer profiles when used in combination with multi-method connector.
  • Search: Fixed an issue that prevented the advanced search filters from working with certain adapters.
  • Transaction List: The URL included in the transaction tree on the transactions details page not link to the transactions view.
  • Transactions: Fixed an issue where sending an amount without specifying a currency would set the amount to 0 for void transactions. This resulted in a full void instead of a partial void.
  • UI: Fixed the tooltips in the screens used to edit connectors.
  • UI: Fixed the responsive styling for the 3DS configuration, making values easier to see.

Adapters

Changed

  • 2C2P (2C2P, 2C2P-EP1-CC): Added the option to ignore scheme fees to the settlement data fetcher configuration.
  • Braintree (BRA-EP2-CC): Added support for a new disbursement file.
  • Braintree (BRA-EP2-CC): The Braintree adapter now supports the new settlement file format for Myanmar.
  • Checkout.com (CHE-EP1): Added the ability to configure a private key for the Checkout.com settlement data fetcher.
  • DPO Pay (PAYGA-PYGT-CC): Added a new Private key parameter that can be configured at the connector level for SFTP servers.
  • EquensWorldline (EQW-EP2): Changed from v2 of the API to the new v3 API.
  • Mastercard Payment Gateway Services (MPG-EP1-CC): Added support for Westpac settlement file handling.
  • Trustly (TRU-EP1): The response status can now be configured and failed payouts are set to FAILED.

Added

  • Straight2Bank (STRAI-E01-MPESA): The Straight2Bank adapter now supports M-Pesa as a payment method.

Fixed

  • American Express (AMX-EP1-AMX): Fixed the handling of chargebacks and chargeback reversals in settlements for American Express.
  • Bank of America (BOFA-EP1-ACH): Fixed an issue that caused export errors due to missing mandatory data.
  • Bank of America (BOFA-EP1-ACH): Fixed an error regarding the export of routing number extra data in the NACHA export for Bank of America.
  • DOKU (DOKU, DOKU-EP01): Added support for refund transactions ini DOKU settlements.
  • DOKU (DOKU, DOKU-EP01): Fixed the mapping of settlement fees and the handling of settlement amounts for the DOKU adapter.
  • DPO Pay (PAYGA-PYGT): The DPO settlement parser has been updated to handle the new CSV structure of the settlement files.
  • DPO Pay (PAYGA-PYG): Fixed the SFTP login to include the mandatory private key.
  • Mashreq (MASH-EP01-CCRD): The default currency for the Mashreq adapter has been changed to QAR.
  • PAYONE (PASIX-EP1-CC): Updated the configration for Six settlements to allow a customer-specific key to be entered.
  • Redsys (RED-EP2-BIZ): Added support for HMAC_SHA256_V1 as a signature version for merchant integrations.
  • Straight2Bank (STRAI-E01): Fixed the handling of refund settlements for Straight2Bank.
  • Trustly (TRU-EP1): Fixed the handling of Trustly credit notification events for payouts to update the status to error and prevent chargebacks from being created.
  • Volt (VOL-EP1): The bearer token status was re-added to the status request header after it was inadvertently removed.
  • Volt (VOL-EP1): Updated the handling of Volt settlement files.
  • Worldline (ING-EP2): Fixed a bug regarding the handling of webhooks.
  • Worldpay (WOR-EP1): Fixed an issue that caused the settlement data fetcher to retrieve multiple settlements if the same settlement file was uploaded more than once.

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.