7 posts tagged with "Customer Profiles"

Gateway Features​

Added​

• Customer Profiles: Add a new flag for the payment selection page to allow storing a payment instrument without automatically linking it to the customer profile.
• Hosted Payment Pages: Add support for the setRequireCardHolder method in PaymentFormV2.
• Job Configuration: Add a new filter Transaction Types to the Collect Transactions by Uploaded CSV File strategy to collect only transactions of the selected types. Not selecting any types will apply no filter.
• Provider Settlements and Reconciliation: Add a new constraint to specify whether transactions are from a merchant of type marketplace.

Fixed​

• Job Configuration: Fix the Collect Transactions by Uploaded CSV File strategy to ignore invalid uploaded files.

Gateway Adapters​

Changed​

• Adyen (ADY-EP3-P24): Add support for the Online Banking Poland payment method. This real-time bank transfer option allows customers to securely pay directly from their bank account and is widely used in Poland for e-commerce transactions.
• checkout.com (CHE-EP1-CC): Add a configuration to enable Account Name Inquiry (ANI) for register transactions.
• dLocal (DLO-EP1-UPI): Add support for the UPI (Unified Payments Interface) payment method. UPI is an instant real-time payment system widely used in India, enabling customers to transfer funds directly between bank accounts via mobile or web applications.
• EquensWorldline (EQW-EP1-CC): Add a new configuration option to select between the old and new Settlement and Reconciliation retrieval logic. By default, the old logic is used.
• JPMorganChase (CHA-EP1-CC): Add support for retrieving and processing a new settlement report entity type Funded Transaction Fee Details (FTI).
• Klarna (KLW): Add a new fee type representing the total VAT amount for settlements.
• PayPal Complete Payments - PPCP (PPCP): Add a new setting to include customer billing and shipping details from PayPal in the callback request.

Fixed​

• DigitSecure (DS-EP1-T2P): Resolve an issue where the Transaction Details page could not be loaded.
• Nuvei (NUV-EP1): Fix a bug where the wrong identifier was stored as the adapter transaction ID.
• Stripe (STRV2-EP1): Fix an issue that prevented configuring reconciliation handling.
• Stripe (STRV2-EP3): Fix an issue that prevented configuring reconciliation handling.
• Worldline (ING-EP8-CC): Fix minor payload change for captures.

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​

Changed​

• Transaction API: Fix an issue where invalid browserScreenHeight or browserScreenWidth values caused errors. Now, any invalid values are properly handled to ensure smooth processing.

Features​

Changed​

• Transaction Processing: Remove the billing country restriction for the iDeal payment method, allowing values beyond NL and BE.

Added​

• Hosted Payment Pages: Add data attributes to the Google Pay button for easier configuration on the Hosted Payment Page (HPP). Supported attributes include data-button-color, data-button-type, data-button-radius, data-button-size-mode, and data-button-locale.

Fixed​

• Customer Profiles:
  • Fix an issue where the action buttons for Payment Instruments in the Customer Profile merchant view were not displayed.
  • Fix a bug where deregistering via the action button in the Customer Profile merchant view did not work properly.
  • Fix a bug where the detach and deregister actions for Payment Instruments in the Customer Profile merchant view did not reset the preferred payment method.
• Pay-by-Link: Fix an issue where Pay-by-Link (PBL) data failed to display when customer information was missing from the transaction; it will now display correctly even if customer data is absent.
• Provider Settlements: Fix an issue when settling preauthorize and void transaction fees.
• Provider Settlements and Reconciliation: Fix an issue in settlement processing where refunds referencing pre-authorized transactions were not correctly matched to their capture transactions.
• Transaction Processing: Fix surcharge calculation for direct PCI API requests.

Adapters​

Changed​

• HUA NAN COMMERCIAL BANK (HNCB-EP2-HBQR): Update the encryption process for the HNCB QR payment method to use the PSP’s encryption endpoint instead of local encryption.
• Volt (VOL-EP1):
  • Add pay-by-link capability.
  • Add JWT signature support for refunds to ensure strong customer authentication (SCA) compliance.

Fixed​

• dLocal (DLO): Fix issue with postback handling by using the correct transaction ID from the currently processing refund transaction, instead of the order ID from the debit.
• PXP (PXP-EP1-CC): Fix the handling of transactionSubType in PSP callbacks to ensure proper support for Rapid Dispute Resolution (RDR).

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​

• Post Processing Setting: Added validation of custom parameters, it will now show an error when trying to save post processing job settings with invalid custom parameters.

Fixed​

• Customer Profiles: Use the network token (dPAN) instead of the fPAN when a customer profile was created or updated from a network token registration.

Adapters​

Changed​

• Valitor (VALIT): Added support for mapping Acquirer Reference Numbers (ARNs) in settlement processing.
• Worldpay (WOR-EP1): Added support for account funding transactions (AFT).

Fixed​

• GoCardless (GOC): Fixed an issue in settlement processing where missing links.payment or links.refund in a refund object would previously cause an error and stop transaction retrieval.
• Klarna (KLW): Fixed Klarna settlement configuration to allow longer passwords via the KlarnaApiPassword field in the provider settlement data fetcher configuration. If no KlarnaApiPassword is set, the connector configuration password will still be used.
• Nexi Group (NETS): Fixes a problem with the test-mode configuration setting which prevented retrieving settlements.
• PayPal Complete Payments - PPCP (PPCP-EP1-PPE): Removed null values from the setup token call to prevent issues with the prepare-register call when shipping details are not provided.
• PXP (PXP-EP1-INST):
  • Added missing adapter specific documentation.
  • Send initiatePaymentFromReferenceRequest.merchantTransactionId to the PSP to correctly link follow-up transactions with their initial transaction.
  • Fixed handling of responses of capture, refund, and void transactions.
• Worldpay (WOR-EP5): Fixed the settlement amount calculation for refunds during settlement processing.

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​

• Provisioning API: Resolved an error in the Provisioning API by adding null checks when building response objects for meta connectors without a default connector.
• Push API: Fixed handling of request bodies with invalid JSON.

Features​

Changed​

• Customer Profiles: Made the action column in the customer profile payment instruments table non-sortable.
• Transaction List: Increased the number of displayed connectors in the advanced search form from 100 to 700.

Added​

• Post Processing Jobs: Added the ability to export transaction extra data in post-processing export strategies, including "Write customized Settlement CSV", "Export Transactions to XLSX (Version 2)", "Export Transactions to XLSX", and "Export Transactions to CSV". Also, added "key" and "default" column configurations to "Export Transactions to XLSX (Version 2)", "Export Transactions to XLSX", and "Export Transactions to CSV".

Fixed​

• Account Updater: Improved the account updater to consider BIN lookup results alongside the card type for more accurate processing.
• Account Updater: Fixed an issue in the Account Updater that caused cards to appear as updated twice in the batch for clients.
• Connector Settings: Fixed a bug that caused the connector settings "Transactions: Expire automatically after (x) minutes" and "Expires pending transactions after given minutes" to not work when added as Global Settings.
• Customer Profiles: Use the correct customer profile container for meta connectors.
• Dashboard: Fixed an issue where the pivot table couldn’t resolve the connector list, causing multiple selections to show as ‘n/a’.
• Dashboard: Fixed a dashboard issue where GUIDs were displayed instead of merchant names.
• Hosted Payment Pages: Removed async from Google Pay JS on hosted payment pages to enable synchronous loading, ensuring the Google Pay button displays reliably.
• Transaction List: Updated transaction list links to ensure they work correctly by including a default status, preventing 404 errors.
• Virtual Terminal: Fixed issues in the Virtual Terminal for direct debit transactions by preventing mandate date validation when the field is empty and correcting format validation to display proper error messages instead of "unknown error".

Adapters​

Changed​

• Klarna (KLW-EP1): Added a connector setting "treat the BACK status from klarna as CANCELLED".
• Mashreq (MASH-EP01): Added support for debit auto-capture.
• PAYONE (PASIX): Add new mappings for settlements:
  • Markup fee (condCode 701)
  • Dispute fee (condCode 55).
• PXP (PXP-EP1-INST): Added support for the in-store card deposit payment method.
• Sepa Express (SEP-EP3-SEP): Added support for settlement handling.
• Worldline (ING-EP2): Always store the adapter transaction identifier if present to properly handle subsequent transactions.

Fixed​

• American Express (AMX-EP1-AMX): Fixed system trace audit number (STAN) issue by using a modulus operation on the transaction ID to ensure it fits within base36 encoding limits.
• iyzico (IYZ): Fixed settlement handling for Iyzico to correctly parse the batch number for all settlement objects.
• Spreedly (SPR-EP1-CC): Fixed date parsing to correctly handle microseconds included by the PSP.
• Transbank (TRANS-TSB1): Fixed handling of empty responses.

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​

• Job Configuration: Strengthened TLS verification for the target host when utilizing the Send document to endpoint post-processing step.

Added​

• Connector Settings:
  • Added a new connector setting Postback/Status: include original adapter reference id in postback request and status response to enable sending extraData["originalAdapterReferenceId"] in callback requests and status responses for all transaction types.
  • Added a new connector setting Postback/Status: include reference uuid for all subsequent transactions in postback request and status response to enable sending referenceUuid in callback requests and status responses for all transaction types. This includes transactions referenced directly via the referenceUuid field, as well as related transactions in the customerProfileData.customerProfileGuid field of the customer profile, provided the customer profile belongs to the affected merchant.

Fixed​

• Customer Profiles: Fixed an issue where manually detaching a payment instrument without deleting it from a customer profile caused unwanted behavior.
• Provider Settlements and Reconciliation: The callback URL for chargebacks initiated through settlement processing is determined automatically. If the related transaction lacks a callback URL, the transaction tree is searched for an appropriate destination.
• User Management: Extended the Include Sub-Tenants filter to include sub-tenants of sub-tenants, not just direct sub-tenants.

Adapters​

Changed​

• Adyen (ADY-EP3-MBWAY): Added support for the MB Way payment method to Adyen Checkout. MB WAY, provided by MULTIBANCO, serves as a mobile wallet within Portugal's interbank payment network.
• checkout.com (CHE-EP2-IDE): Added support for the iDEAL payment method using the checkout.com NAS platform. 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.
• Klarna (KLW-EP1):
  • Added documentation on required parameters.
  • Added fallback logic to populate essential customer fields when shipping data is missing.
• Worldline (ING-EP2): Added support for the Sofort payment method. Sofort is the predominant online banking method in countries such as Germany, Austria, Switzerland and Belgium and continues to expand its global reach.

Fixed​

• 2C2P (2C2P-EP1): Improved the handling of empty HTTP responses received from 2C2P.
• Alignet (ALI-EP01-CC):
  • Updated documentation to clarify that customer shipping address first and last name parameters are optional.
  • Included extraData from referenced transactions in follow-up transactions.
• Bitpay (BTP-EP1): Fixed cancelUrl forwarding to Bitpay and introduced logging for Bitpay invoice adapter calls.
• Braintree (BRA): Skip loading transaction data when receiving Braintree callbacks without a paymentId.
• checkout.com (CHE):
  • Fixed an issue where settlement processing failed if a previous data fetcher returned no data.
  • Updated documentation with more detailed information about extraData fields relevant to the recipient of account funding transactions.
• Sepa Express (SEP): Improved UTF-8 handling in the account holder field to handle invalid characters more effectively.
• Unzer (UNZER-EP1): Fixed an issue with handling empty responses from the PSP.
• Volt (VOL-EP1): Enhanced callback processing to immediately mark transactions as successful upon receiving a COMPLETED status callback and the successOnSettle connector setting is enabled.
• Worldline (ING-EP2): Fixed an issue with follow-up debit transactions that reference transactions based on imported IBAN tokens.

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.