3 posts tagged with "Customer Profile"

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.

API​

Fixed​

• Batch API: Addressed issues with the conversion of files from CSV to JSON, and conflicting UUIDs due to latency between the time when a transaction is submitted and actually processed.
• Transaction API: Fixed an issue where if a failover transaction returns a merchant advice code, this MAC is not returned by the origin transaction. The MAC is now returned by the origin transaction.

Features​

Changed​

• Customer Profile: It is now possible to use the UUID or payment token from a customer profile to request a CVV refresh via payment.js. This makes it possible to ask the customer to enter their CVV for transactions using a stored credit card.
• Post Processing Setting: Postback notifications are now sent when creating an "unknown" transaction.
• UI: Information on the possible impact of daylight savings time is now displayed when editing job schedules.
• User Management: Any changes to merchant users now require additional confirmation, and a message is displayed that these changes may have an effect on live processing.

Fixed​

• Global Connector Settings: Transaction expiry settings are now displayed in the connector's global settings section.
• Post Processing Job Configuration: The calculation of the net settlement amount in the "Write customized Settlement CSV" job step is now the same for refunds and chargebacks.
• Risk Profile: The "Allowlist" and "Blocklist" risk rules no longer list credit card-related options such as the BIN and CC fingerprint for the meta-connector, as the card cannot be evaluated at this stage of processing.

Adapters​

Changed​

• Bitpay (BTP-EP1-CR): BitPay pairing has been moved to the connector's Additional Configuration tab.
• dLocal (DLO-EP1): Support has been added for PuntoXpress and PayCash in Costa Rica.
• HUA NAN COMMERCIAL BANK (HNCB-EP2-HBQR): The key version used for encryption is now a configuration option.
• Paynetics (PNE-EP1-CC): Added API documentation for Paynetics.
• PAYONE (PASIX-EP3-CC): Added API documentation for Payone.
• Worldline (ING-EP2-CC): Fixed an issue where tokens are flagged as single use when they should be flagged as recurring. These tokens can now be reused.

Added​

• Adyen (ADY): Added a new data fetcher for settlements provided by Izyico.
• Zona Virtual SA - Zonapagos (ZONA): Zona Virtual is a Colombian company with 23 years of experience in the e-commerce sector. The ZonaPagos adapter support payments via credit card and Pagos Seguros en Línea.

Fixed​

• checkout.com (CHE): Added support for "Partial Capture" settlement entries.
• GoCardless (GOC): Fixed an issue with register transactions in the new server-to-server flow.
• Nuvei (NUV-EP1-CC): Updated the API documentation to include mapping information.
• Shift4 (CRE-EP1-CC): Fixed an issue with how UUIDs are formatted in failover transactions.
• Sofort (SOF-EP2-SOF): Fixed an issue with refunds that would change the status of the original transaction from success to error.
• Unzer (UNZER-EP1): The orderId in capture requests now uses the additionalId1 in the preauthorize transaction.
• Valitor (VALIT-EP1-CC): Fixed an issue with duplicated preauthorize transactions in settlements.

Misc​

Added​

• API Documentation: Updated the API documentation to include information on the bin_digits parameter.

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​

• 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 and Reconciliation: 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.