Skip to main content

24 posts tagged with "Worldline"

View All Tags

Gateway — v25.18

Gateway Features

Added

  • Account Updater: Add a configurable setting to specify the update interval for expired cards. Requires the merchant.account-updater.custom-interval permission.
  • Connector Settings: Add a new connector setting to disable network token processing.
  • Job Configuration: Add an option to skip the SFTP upload when no matching file is found for the Upload document to SFTP server export step.
  • Multi-method connector: Add a new setting to display all payment methods for transactions with withRegister=true, regardless of whether they support recurring payments. If the selected payment method does not support recurring payments, the withRegister flag will be set to false. For customer profiles, the payment instrument will not be stored in that case.
  • Virtual Terminal: Add support for split transactions in the Virtual Terminal.

Removed

  • Network Tokenization: Remove transaction indicator requirement check for subsequent network token transactions.

Fixed

  • Transaction Processing: Fix an edge case where the transaction token is not properly stored.

Gateway Adapters

Changed

  • American Express (AMX-EP1-AMX): Update the settlement parser to support the new Global Raw Data Reconciliation File (GRRCN) version 4.01 (up from 3.01).
  • PayU (PAU-E01-CC):
    • Add support for installments.
    • Enable recurring transactions.
  • PayU (PAU-E01-PAE): Add a default expiration date of 1 day.

Fixed

  • dLocal (DLO): Fix the private key field in the provider settlement configuration.
  • GoCardless (GOC-EP1-BT): Fix handling of the transaction status in the mandate flow.
  • PayPal Complete Payments - PPCP (PPCP-EP1): Add support for additional transaction update callbacks.
  • Worldline (ING-EP5): Fix parsing of error codes and error messages.

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 — v25.9

Gateway Features

Changed

  • Transaction Details: Extend the Create Manual Chargeback and Create Manual Chargeback Reversal action to allow setting the settlement amount, settlement currency and settlement date.

Added

  • Transaction Details: Add support to manually create a second chargeback.

Fixed

  • Connector Configuration: Fix an issue for the connector setting Accept postbacks from other connectors where postbacks were processed through the wrong connector.
  • Provider Settlements and Reconciliation: Fix an issue handling settlements for transactions sharing the same ARN.
  • Transaction Details: Fix incorrect status display for subsequent transactions on the transaction detail page.

Gateway Adapters

Changed

  • Adyen (ADY-EP3-PAYPA): Add support for the new payment method PayPay. PayPay is a Japanese e-wallet allowing customers to either pay directly in the app or by scanning a QR code.
  • Adyen (ADY-EP4-CC): Add support for Refund and Payout.
  • DPO Pay (PAYGA-PYGT-CC): Add status retrieval for transaction communication errors (previously only for timeouts).
  • PPRO (PPR-EP1-TRU): Map the customer.email parameter to PPRO's useremail request parameter.
  • Redsys (RED-EP2): Add a new configuration to enable or disable sending Merchant Card-on-File transaction indicators for register transactions (DS_MERCHANT_COF_TYPE = R, DS_MERCHANT_COF_INI = S).
  • Worldline (ING-EP2-IDE): Add documentation for the payment method iDeal.

Fixed

  • American Express (AMX-EP1): Fix chargeback settlement amounts where wrongly saved negative values were leading to conflicts.
  • PayU (PAU-E01-MAS): Fix an issue when using customer profile tokens for subsequent transactions.
  • PPRO (PPR): Update the postback validation to support SHA-256 hashing.

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 — v25.8

Gateway API

Changed

  • Transaction API: Update API validation for the browserTimezone field in 3DS data to accept values prefixed with a plus sign (e.g., "+0300"), which were previously rejected, and to enforce a maximum string length of 4 characters for this field.

Added

  • Customer profiles API: Add attachPaymentInstrument and detachPaymentInstrument API endpoints to customer profiles, allowing users to attach or detach payment instruments using profile identifiers (GUID or customer identification) and a transaction UUID.

Gateway Features

Added

  • Connector Settings: Add a new connector setting Disable Refund After Chargeback, which controls whether the refund option is available for transactions that have undergone a chargeback.

Gateway Adapters

Changed

  • Adyen (ADY-EP4-CC): Add support for preauthorize and capture transactions.
  • checkout.com (CHE-EP2-BIZ): Add support for the new payment method Bizum. Bizum is a fast and secure mobile payment method widely used in Spain.
  • dLocal (DLO-EP1-SINMO): Add support for the new payment method Sinpe Móvil. SINPE Móvil in Costa Rica facilitates money transfers through SMS, allowing users to send funds to another mobile phone number without needing the recipient’s bank account information.
  • PAYONE (PASIX-EP1): Add documentation for the extraData.avsCheck field, which is used to enable Address Verification System (AVS) checks.
  • Worldline (ING-EP2-IDE): Add support for the new payment method iDeal. iDEAL is an online payment method that enables consumers to pay online through their own bank. Payments are made via bank app or online banking.
  • Worldpay (WOR-EP1-KLAPN): Update documentation to specify that item.totalAmount is a required field for the payment method Klarna.

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 — v25.7

Gateway Features

Added

  • BIN Lookup: Add the BIN segment to the transaction details view in the admin and merchant portals.
  • Connector Settings: Add the Copy Description to Chargeback Reversal connector setting. When enabled, the description from the original transaction will be copied to the chargeback reversal.
  • Connector Settings: Add the Copy Merchant Meta Data to Chargeback and Copy Merchant Meta Data to Chargeback Reversal connector settings. These settings enable the copying of merchant metadata to newly created chargebacks or chargeback reversals initiated through Settlements or Reconciliations.
  • Transaction Processing: Add Japanese translations for the loading screen that appears after a customer submits the payment or 3DS form for transactions requiring additional processing time.

Gateway Adapters

Changed

  • checkout.com (CHE-EP2): Add documentation for the extraData.recipientDateOfBirth and extraData.senderDateOfBirth parameters in the AFT section of the connector documentation.
  • Nexi Group (NETS-EP2): Improve the description of error messages for the connector.
  • Paymob (PMO-EP2-CCRD): Add the bank_installments_integration_id and bank_installments_enabled connector settings. When both settings are configured, the bank_installments_integration_id will be included in the PSP payload, allowing users to select installments as a payment option in the payment modal for credit card redirects.
  • Worldline (ING-EP2, ING-EP7): Add the shouldBeFinishedWhenCapturedSofort connector setting. When enabled, Sofort debit transactions will be marked as successful when the status changes to captured.

Fixed

  • DPO Pay (PAYGA-PYGT): Fix an issue where the transaction status in the adpater could be incorrect after a timeout by the PSP. The platform now polls the status API to ensure the correct transaction status is set.
  • Redsys (RED-EP2-BIAPI): Maintain and update the payment service provider's transaction ID from the initial transaction in subsequent 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.

API v2, Gateway, Payment Services v2 — v25.1

Gateway Features

Fixed

  • Job Configuration: Fix a bug in the post-processing job configuration where endpoint URL validation in the Send document to endpoint exporting configuration incorrectly restricted URL paths to lowercase only.

Gateway Adapters

Changed

  • KCP Mobile, KCP PC (KCPMO-EP1, KCPPC-EP01): Add extra data to callback and API response, including card acquirer code (extraData.acqu_cd), card issuer code (extraData.card_cd), payment method (extraData.pay_method), truncated PAN (extraData.card_no), and bank code (extraData.bank_code).
  • PayPal Complete Payments - PPCP (PPCP-EP1): Add chargeback protection details to API response, including seller protection status (extraData.seller_protection_status), dispute categories (extraData.seller_protection_dispute_categories), and PayPal account status (extraData.paypal_account_status).
  • Stripe (STRV2): Add support for account funding transactions (AFT).
  • Worldpay (WOR-EP1-CC): Add documentation about the extraData.refundAuthorisationReference parameter returned in callbacks.

Fixed

  • PXP (PXP-EP1-INST): Fix a typo in an error message.
  • Worldline (ING-EP1, ING-EP2, ING-EP3, ING-EP4, ING-EP7): Fix chargeback handling in the settlement and reconciliation parser.

API v2

Added

  • APIv2’s NetworkToken endpoints now return an error if multiple Network Tokens exist for a single token, requiring the new tokenReferenceId parameter to specify which one to use.

Payment Services v2

Added

  • Add Merchant Advice and Brand Auth Response code mappings to AdyenDirect, FirstDataIPG, and Orbital gateways for additional insights on how to handle failed 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.