6 posts tagged with "Pay-by-Link"

Gateway API​

Changed​

• Customer profiles API: Add the option to either detach or to detach and deregister payment instruments.
• PCI API: Add surchargeAmount, gstAmount, and totalAmount to the transaction response whenever a surcharge is present.

Gateway Features​

Changed​

• Customer Profiles: Extend the use of stored payment instruments to multi-method connectors and wallet connectors.
• Pay-by-Link: Add the ability to include values determined after payment processing (e.g. external risk check) in the result page.

Fixed​

• Network Tokenization: Fix an issue where wallet transactions were submitted for network tokenization.
• Network Tokenization: Fix an edge case where the system attempts to use a non-existent network token.
• Pay-by-Link: Fix an issue when cancelling an ongoing transaction.
• Transaction Details: Fix duplicate BIN lookup entries being added to the transaction log.
• Transaction Processing: Fix an issue where Apple Pay and Google Pay transactions could fail with an incorrect token error in certain scenarios.

Gateway Adapters​

Changed​

• Dimoco (DIM): Match fraud records (SAF + TC4) to transactions and flag them as fraud.
• Euronet (EUR): Add support for payouts.
• JPMorgan Chase (CHA): Update documentation for ACH Direct Debit.
• PayPal Complete Payments - PPCP (PPCP): Add support for multiple billing agreements between the merchant and the customer which can be configured either via connector config or extra data.
• Worldline (ING-EP5-CC): Add support for network tokens.

Added​

• MerchantE Solutions (MES): MerchantE Solutions is a US-based payment processor and gateway, enabling secure Credit Card payments for e-commerce merchants. The new adapter supports Debit, Preauthorize, Capture, Void, and Refund transaction types.
• Reflect (REF): New push adapter Reflect, a digital mobile banking app in Jordan powered by Arab Bank that offers seamless money management, digital transfers, and daily financial services.
• Upay (UPAY): New push adapter Upay, a mobile financial service in Bangladesh offering fast, secure money transfers, bill payments, and mobile recharges.
• USIO (USIO): USIO is a US-based payment processor offering integrated credit card and ACH payment solutions. The new adapter supports the payment method ACH for transaction types Debit, Register, Void, Refund, and Payout. ACH (Automated Clearing House) is an electronic funds-transfer network in the United States, enabling bank-to-bank payments.

Fixed​

• Dimoco (DIM):
  • Fix the foreign exchange gain/loss handling in the reconciliation process.
  • Fix an issue where reconciliation records are occasionally being matched to the wrong transaction due to shortened reference ids.
• eMerchantPay (EME-EP3): Fix an issue where customer data was missing on recurring transactions.
• JPMorgan Chase (CHA-EP3-ACH):
  • Fix an issue with the hosted payment page flow.
  • Fix a bug where the transaction status is prematurely set to success.

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.

API​

Changed​

• Provisioning API: Added the field eventNotificationUrl to merchant entities.
• Transaction API: Added field transactionSubType to the status API calls and to transaction callback bodys.

Features​

Changed​

• BIN Lookup: Updated the BIN data source.
• Pay-by-Link: Introduced a new pay-by-link-enabled permission to allow control over which API users can trigger pay-by-link transaction., The permission defaults to enabled for existing API users who have previously used pay-by-link, and disabled for all others.
• Transaction Processing: Enabled sending transaction descriptions to upstream PSPs for void and capture transaction types.

Added​

• Account Updater (Network Tokenization): Added a notification service that sends callbacks to shared merchants —those sharing a customer profile container— whenever a transaction is updated through the account updater or NTS Updates.

• Fee Management: Added a new field Transaction Subtype to Fee Constraints, including it in fee calculations; subtypes can be Chargeback Resolved, Chargeback Reversal Resolved, or - any - for no specific preference. Fee items will now be grouped by transaction type and subtype (if present).

• Job Configuration: Introduced transaction subtype filtering to the following Collecting Post Processing Job steps:

  • Collect Transactions from Related Batch
  • Collect All Transactions within a Period
  • Collect Transactions from Provider Settlements (created/settled within a period)
  • Collect Transactions by Settlement State

  Introduced transaction subtype filtering and grouping to the following Processing Post Processing Job steps:

  • Aggregate Transaction Fees to Job Line Items
  • Aggregate Transaction Values to Job Line Items
  • Calculate Rolling Reserve for Merchant
  • Count Transaction Value to Job Line Items.

• Post Processing Jobs: Added support for filtering via the transaction subtype in the transaction view for Post Processing Jobs.

• Post Processing Jobs: Added transaction subType column as possible export value for the following Post Processing Job steps

  • Export Transactions to CSV
  • Export Transactions to XLSX
  • Export Transactions to XLSX (Version 2)
  • Write customized Settlement CSV.

• Provider Settlements and Reconciliation: Added support for filtering via the transaction subtype in the Transactions in Batch and Conflicted Transactions views for Provider Settlements.

• Transaction Details & Post Processing Jobs & Provider Settlements and Reconciliation: Added subtype to the transaction Details view.

• Transaction Processing: Added a subtype field to transactions for rapid dispute resolution, with available subtypes "chargeback resolved" and "chargeback-reversal resolved".

Fixed​

• Post Processing Setting: Set a default transaction type when creating transactions derived from settlements without a transaction type.
• Transaction Details: Fixed an issue where displaying Risk Data on the Transaction Detail page could cause an error in certain cases.
• Virtual terminal: Fixed the virtual terminal view for merchant users.

Adapters​

Changed​

• Amazon Payment Services (AMAZO-EP1): Added clear error messages for transactions when errors are triggered by incoming postbacks.
• MultiSafepay (MUL-EP1): Added Content-Type: application/json to requests sent to the PSP to ensure the PSP can look-up the requests in their logs.
• Valitor (VALIT): Added support for RDR.

Added​

• Bangkok Bank (BB): Added the Bangkok Bank post processing adapter with support for settlement handling.

Fixed​

• Global Payments (GBP): Resolved a bug in the parsing of Global Payments settlements.
• GoCardless (GOC-EP1): Removed mandate callback handling for cases where the initial registration was already successful.

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​

Added​

• Provisioning API: Two new fields have been added to the merchant response model: ntsEnrollmentStatus and networkTokenizationEnabled.

Features​

Changed​

• Job Configuration: Information on inherited job type templates is now displayed, informing users as to why the template cannot be edited.

Added​

• Network Tokenization:
  • Information on the status of enrollment for network tokenization is now available in the base data for a merchant. A new line, "Network Tokenization" has been added. If the merchant has a TRID assigned, the status is displayed as "enabled" when viewing the data as an admin with the permission "tokenization.networkTokenization.enrollment.show".
  • Merchants can now be filtered by their NTS status in the overview.

Fixed​

• Pay-by-Link: Fixed an issue with the virtual terminal's result page not updating correctly if the initial transaction fails. Instead of displaying transaction data from the most recent (successful) transaction, data from the first (failed) transaction continued to be displayed.
• Provider Settlements and Reconciliation: Fixed an issue that would cause chargeback reversals to be created for the debit transaction, instead of the chargeback transaction.
• Transaction List: Fixed an issue that would cause an error in the advanced search when changing the comparison operator from a range to any other operator.
• Transaction List: Fixed an issue with sorting credit card fields. Note that BIN data cannot be sorted.
• User Management: The frontend.statistics.show permissions now governs access to the pivot table as well.
• Virtual Terminal: Fixed an unhandled exception in the virtual terminal that would occur if the fee set or fee entity was not found. The exception is now handled and an empty surcharge value is returned.

Adapters​

Changed​

• Adyen (ADY): The payment reference for settlements is now saved.
• Amazon Payment Services (AMAZO): It is now possible to filter transactions by the status "Accepted".
• MultiSafepay (MUL): Added the chargeback reason for chargebacks.
• Stripe (STRV2-EP1-MAS): Additional data from the Stripe API response is now included in the postback's extraData.

Added​

• dLocal (DLO-EP1): Added support for the Sinpe payment method. This method supports bank transfers in Costa Rica.
• Worldline (ING-EP2): Added support for payments via Trustly.
• Zona Virtual SA - Zonapagos (ZONA-EP1-ZP): Added a generic payment method that redirects to the Zona Pagos payment page. The consumer can then select the desired payment method on this page to initiate the transaction.

Fixed​

• Adyen (ADY-EP3-BIZ): Fixed an issue that would cause transactions that had been processed successfully to be assigned the status error or pending.
• checkout.com (CHE): Fixed an issue that would cause an error when retrieving the session ID.
• eMerchantPay (EME-EP3-SEP): Fixed an error that would occur if the customer was not an IBAN customer.
• Mashreq (MASH): Fixed an issue when checking 3DS credentials that would cause a type error.
• Mercado Pago (MERPA-PROD): Fixed an issue with register transactions caused by the Amount For Card Verification not being included in the request to retrieve the issuer and payment method ID from the PSP.
• Skrill (SKR-EP1): Fixed an issue related to email addresses not being tied to a Skrill account when requesting a payout. This would cause the payout to fail.
• Volt (VOL): Fixed an issue caused by incorrectly handling errors in a response as a result.

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​

Added​

• Job Configuration: To simplify the process of exporting settlement file data for enterprises with multiple merchants, the External ID stored in the provider can now be used to store an identifier for each merchant. This ID can be selected in export jobs, allowing the same export job to be used for each company/merchant in cases where there are otherwise no differences between the exports. Previously, an individual export needed to be configured per company/merchant.

Fixed​

• Account Updater: Fixed an issue with the Account Updater that would lead to an incorrect Status being displayed for batch updates ("Finished" instead of "Waiting").
• Account Updater: Fixed an issue with the new merchant overview where clicking on the details would not redirect users to the selected merchant, but to the selected tenant instead.
• Merchant Interface: Updated some translations and reviewed the Croatian and Slovenian translations.
• Pay-by-Link: Restricted the ability to cancel transactions to pay-by-link transactions only.
• Post Processing Setting: Fixed an issue that would prevent settlements from being retrieved if the waitForAllFiles setting is enabled. Incomplete periods are now also handled correctly, with the last period only being updated if settlement files were processed.
• UI: Fixed the 8-digit BIN display in the transaction details view.
• UI Navigation: Fixed the broken icon for creating connectors.
• Virtual Terminal: Removed trailing apostrophes for virtual terminal result URLs.

Adapters​

Changed​

• American Express (AMX-EP1): Reinstituted a change that was reverted in the last release. A reference number is generated and passed to the vault as part of the capture request using the additionalId1 field. However, this could not be handled using the multi-method connector.
• ATOM (an NTT DATA Company) (ATOM-EP1-CC): The data fetcher configuration has been updated, allowing additional field mappings for settlement files. The names of the fields selected here need to be added to the key column in the export job.
• checkout.com (CHE-EP2): Added payout parameters for platform 2.
• dLocal (DLO-EP1-PUNTO): The Punto Express payment method is now supported by the dLocal adapter.
• eMerchantPay (EME-EP3-SEP): Added support for deregister transactions.
• GoCardless (GOC-EP1): An additional configuration option has been added for the connector that provides a choice between redirect and server to server flows.
• Nuvei (NUV-EP2): Fixed the mapping of Nuvei error codes, with "Service Busy" now being mapped to IXOPAY error code 3003 (temporarily unavailable).
• Sepa Express (SEP-EP3-BTR): Added a new bank transfer payment method to the adapter. As this payment method uses open banking, some transaction types like register and deregister are unavailable, along with other transaction types not implemented in the original version of the adapter.
• SoftBank Payment Service (SOB-EP1): The documentation was updated to include information on required fields.
• Unzer (UNZER): Fixed the title for the Unzer API documentation.
• Valitor (VALIT-EP1-CC): Fixed an issue that would cause refunds to fail for capture transactions. Instead of requesting a refund, IXOPAY now requests a capture refund, which resolves this issue.

Added​

• AsiaPay (ASIA): AsiaPay is a leading payment service provider in the APAC region. The adapter supports GCash, ShopeePay and credit card payments.
• HypYaad (HYP-EP1-CC): Hyp is an Israeli all-in-one payments solution that provides online and in-store payment solutions. The adapter supports credit card payments.
• Unzer (UNZER-EP1): Unzer is a leading fintech company based in Germany, specializing in providing innovative and secure payment solutions. With a strong focus on e-commerce, Unzer offers a wide range of payment methods and services.

Fixed​

• American Express (AMX-EP1): Fixed an issue with fees in American Express settlements that would only occur under certain circumstances.
• AsiaPay (ASIA): The AsiaPay PesoPay logo is now displayed wherever the brand name is used instead of the adapter name.
• checkout.com (CHE-EP1): Fee reports are now handled in a second process, rather than as part of the settlement. A new data fetcher configuration (gross type) is available for this purpose.
• Klarna (KLW): Fixed an issue with validation that affected customers in specific locations. The validation now checks that the billingState is set if the country is US or Australia.
• Nuvei (NUV-EP1): Improved the parsing of the CSV settlement files to be more robust. Under some circumstances, an error could occur when parsing settlement files.
• Nuvei (NUV-EP1): Before parsing a row in the reconciliation file, the date is checked to ensure it is valid.
• Straight2Bank Pay (STRAI-E01): Fixed an issue that would cause the retrieval process for settlements to be locked if an invalid response was received.
• Unzer: Fixed errors caused when postback sharing is not set in the connector.
• Worldpay (WOR-EP1-CC): The adapter transaction ID is now set when an incoming postback 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.