Skip to main content

12 posts tagged with "Worldline"

View All Tags

v.23.22

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.

v.23.19

API

Added

  • Transaction API: Added dedicated fields for the cardholder billing state (billingAddressState) and cardholder shipping state (shippingAddressState) used in 3DS authentication.

Features

Changed

  • Permissions: Front end user roles have been split into view and edit permissions.
  • UI: Autocompletion of password input fields has been disabled as a security measure.

Fixed

  • Multi-method Connector: Fixed an issue with converting register transactions to debit/preauthorize transactions for adapters that do not support register transactions directly. This conversion would fail when using multi-method meta-connectors in conjunction with the processing:convert-register-to-debit setting.
  • Post-processing Schedule: Fixed an issue in calculating the post processing schedule interval.
  • UI: Fixed the Token icon colour for white label tenants.

Adapters

Changed

  • Klarna (KLW-EP1-APM): In order to support an upcoming change, the IXOPAY UUID is now provided via the merchant_reference1 and merchant_reference2 fields. IXOPAY now checks for the UUID in merchant_reference2 when handling settlements, using this value as a fallback until changes to the handling of the UUID are complete.
  • Mashreq (MASH-EP01-CCRD): The response data is now used to set the transaction status instead of sending a separate request to retrieve the status.
  • Valitor (VALIT-EP1-CC): Changed the Valitor ID used to map settlements, as the ID used previously could not handle certain cases such as refunds.

Added

  • Adyen (ADY-EP3-BIZ): Bizum has been added as a new payment method.
  • AsiaPay (ASIA): AsiaPay is an Asian digital payment service provider, covering credit and debit cards, online banking, digital wallets, BNPL and other digital payments. The new adapter supports GCash, BPI and ShopeePay as well as credit card payments with JCB and Mastercard.

Fixed

  • eMerchantPay (EME-EP3): Fixed issues with invalid amounts that occurred when the currency is missing by using the related transaction's currency as a fallback.
  • Worldline (ING-EP2-CC): Updated the adapter to use the same error mapping for adapter calls and incoming callbacks.

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.15

Features

Changed

  • API: The Transaction API has been updated to allow pay-by-link transactions to be cancelled with an API call using the URL supplied in the initial response.

Added

  • Account Updater: A new view has been added to the Account Updater, showing all merchants for the selected tenant, and permissions can now be set to view the enrollment status of merchants in the overview.

Fixed

  • Fee Management: Fixed an issue that prevented fees from being configured if no fee set had been added for the connector.
  • Post Processing: Fixed an issue that caused the post-processing job to fail when settlement reports were uploaded without a header.
  • Transaction Details: Fixed an issue where the payByLink and the surcharge transaction data was not copied to the new retry transaction when retrying a transaction.
  • Virtual Terminal: Added support for the Montenegrin language to the virtual terminal.

Adapters

Changed

  • Bank of America (BOFA-EP1-ACH): Added AchData return data for API results, status responses and callbacks.
  • Bank of America (BOFA-EP1-ACH): Added support for register and follow up debit transactions.
  • MultiSafepay (MUL): Added a new customer extraData parameter, locale, which maps directly to the MultisafePay locale parameter.
  • Worldline (ING): Added support for refund transactions in settlements.

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.

v.23.13

Features

Added

  • Post Processing Jobs: Added a new configuration option in the job configuration Processing Step: Copy Line Items from related batch - Do not aggregate line items with the same name that allows two line items with the same name.
  • Provider Settlements: Added a new Provider Setting - Reconciliation: Create Provider Settlement with Conflict Log to handle settlements provided via reconciliation (e.g. PayPal) in cases where the transaction is missing or unknown.
  • UI Navigation: The Customer Profiles and Account Updater have been moved to the Tokenization menu.

Adapters

Changed

  • checkout.com (CHE-EP1): Aggregated payout information is now represented as line items in settlements. This includes interchange fees, scheme and network fees, provider fees, gateway fees and chargeback fees.
  • DPO Pay (PAYGA-PYGT-PMR): Updated the parser to handle the updated structure in newer settlement files.
  • eMerchantPay (EME-EP3): Removed the check that data has been entered in mandatory fields in EMPGenesis, as these mandatory fields can be disabled for the merchant by the PSP.

Added

  • Braintree (BRA-EP1-PPE): Added support for additional data (STC, AID, BN) required by Braintree for airlines and travel merchants when using PayPal as the payment method.
  • Braintree (BRA-EP1-PPE): Added support for tenant-specific BN code which are included with pre-authorization and debit transactions.
  • Braintree (BRA-EP2-CC): Added support for level 2/3 data for Visa and Mastercard transactions via Braintree.
  • Mashreq (MASH-EP01-CCRD): Added a new adapter for Mashreq. Mashreq a leading financial institutions in the UAE that provides banking and financial services. The adapter supports credit card transactions and settlements.
  • MultiSafepay (MUL-EP1): Added support for reconciliation and settlements for the Multisafepay adapter.
  • PayPal (PPA-EP1-PPE): Wallet data (first name and last name) is now exposed under Additional Info for payouts and debits.
  • Worldpay (ING-EP2): Added the option to configure an SFTP host and SFTP private key with optional SFTP passphrase instead of an SFTP password.

Fixed

  • BDO (BDO-EP1-GCASH): Risk check are now correctly applied to the BDO adapter.
  • DPO Pay (PAYGA-PYGT-CC): Added a check for a mandatory description in refunds.
  • PayPal (PPA-EP1-PPE): Fixed an issue handling the refund amount in partial refunds received via postback.
  • PayU (PAU-E01-CC): Implemented a method for tokenizing cards using debit and refund transaction for Colombia, as authorization and register transactions are not supported.
  • Redsys (RED-EP1-CC): Fixed an issue with the key length in the paramsKey extraData parameter.
  • Volt (VOL-EP1): Fixed error handling during Volt settlement notification handling.
  • Volt (VOL-EP1): By default the full list of banks is now retrieved for Volt. A subset of banks can be retrieved using parameters.page and parameters.limit.
  • Worldline (ING-EP3-CC): Fixed Worldline Ogone TWINT settlement refund fee handling.

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.