24 posts tagged with "Provider Settlements and Reconciliation"

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.

Gateway Features​

Fixed​

• Callback: Postback notifications that previously failed due to DNS lookup issues will now be queued for retries.
• Callback: Add additional transaction logs when callback notifications fail due to DNS lookup issues.
• Fee Management: Adjust the default value for the fee configuration form to prevent unexpected configuration changes.
• Provider Settlements and Reconciliation: Fix an issue where refund transactions received via settlements were not created when the connector setting Provider Settlement: Create unknown transactions was enabled.
• Transaction List: Fix an issue where no transactions were returned when filtering by multiple UUIDs in Live mode.

Gateway Adapters​

Changed​

• 2C2P (2C2P-EP1): Update test and production endpoints.
• Adyen (ADY-EP1-CC): Map additionalData from Adyen to extraData.additionalPspResponse in API responses and callbacks (JSON-encoded) when enabled via a new connector configuration.
• Stripe (STRV2-EP1): Add support for reconciliation.
• Stripe (STRV2-EP3): Add support for reconciliation.

Fixed​

• dLocal (DLO): Treat adjustment lines as settlement meta 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.

Gateway Features​

Changed​

• Provider Settlements and Reconciliation: Rename Reconciliation Conflicts page to Provider Reconciliations.
• Risk Profile: Rename Cumulative Score column to Total Score.

Added​

• Connector Settings: Add a new connector setting Postback: Defer sending until after the API response has been returned.

Fixed​

• Transaction Processing: Fix an issue that could cause a Token not found error in certain circumstances.

Gateway Adapters​

Changed​

• dLocal (DLO-EP1-MP): Add support for the new payment method MultiPago. MultiPago is a cash-based payment method in Latin America that allows customers to pay for online purchases using payment slips at convenience stores or banks.
• Nuvei (NUV-EP1-ALIUN): Add support for the new payment method Alipay+ Unified Payment. Alipay+ Unified Payment is a cross-border digital payment solution that allows customers to pay with various supported e-wallets and other payment methods across multiple regions.
• Nuvei (NUV-EP1-RAKUT): Add support for RakutenPay, a Japanese e-wallet that lets customers pay online or in-store via the app or by scanning a QR code.
• PayPal Complete Payments - PPCP (PPCP): Add support for sending transaction context if data is provided.
• PayPal Complete Payments - PPCP (PPCP-EP1-PPE): Add a new setting useProvidedMerchantUrls to fix mobile payment processing for merchants using PayPal's iOS/Android SDK.

Fixed​

• Cybersource (CYS-EP1-CC): Fix mapping of transaction indicators to the commerceIndicator.
• JCC Payment Systems (JCC-EP1-CC): Fix mapping and handling of callback notifications.
• KakaoPay (KAKAO-EP1-KAKAO): Fix refund handling to ensure each refund is correctly matched and settled.
• Worldpay (WOR): Ensure correct behavior for debit transactions by setting delay capture to 0.

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 Features​

Added​

• Provider Settlements and Reconciliation: Add ability to manually upload reconciliation files.

Fixed​

• Post Processing Setting: Fix a bug where setting a provider's adapter to - caused an error.
• Transaction Processing: Improve handling of follow-up transactions to prevent errors after deregistration.

Gateway Adapters​

Changed​

• Adyen (ADY): Improve error mapping to consider the reason value when provided.
• Adyen (ADY-EP4): Add documentation for referenced and unreferenced Refunds.
• Certegy (CERTE-EP1-ACH): Fix Register and Refund handling.
• DPO Pay (PAYGA-PYGT): Add support for Partial Refunds.
• PPRO (PPR-EP1): Update the endpoint from https://api.girogate.de to https://simpleapi.ppro.com.

Fixed​

• Adyen (ADY-EP3): Fix an issue where extra data was not forwarded for Refunds.
• Bangkok Bank (BB): Fix handling of negative VAT values for settlements.
• dLocal (DLO): Fix an issue with parsing settlement files.

iFrame​

Added​

• UT iFrame: Export TypeScript types from main entry point for standard importsConfiguration, Authentication, HMACAuthentication, and other key types now available. Resolves issue requiring non-standard import paths from node_modules.

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 Features​

Changed​

• Meta connector: Remove the option to change the type of an existing meta-connector (routing / multi-method) to prevent unexpected behavior and ensure consistent functionality.

Added​

• Connector Settings: Add a new connector setting Add Hard Decline Error Codes which allows specifying additional error codes that prevent failover transactions.

Fixed​

• Connector Settings: The connector setting Accept postbacks from other connectors will now properly ignore meta-connectors if provided in the list.
• Provider Settlements and Reconciliation: Fix an issue where a transaction was not settled correctly if a fee-only settlement in a different currency was received before the actual transaction settlement.
• Transaction Processing: Transactions with an expired or non-existent transaction token will no longer be retried.
• User Management: Fix a minor display inconsistency in the permissions list when configuring roles.

Gateway Adapters​

Changed​

• Adyen (ADY-EP4-CC): Add additional data mappings and documentation.
• Amazon Payment Services (AMAZO): Add settlement handling.
• Amazon Payment Services (AMAZO-EP1-NAP,AMAZO-EP2-NAP): Add support for the new payment method NAPS. NAPS is Qatar's national debit card network which offers a convenient, card-independent local payment method, enabling seamless, real-time transactions between businesses and Qatari shoppers across participating Qatari banks.
• Bangkok Bank (BB): Adjust settlement handling to support a new VAT format with VAT provided once per file instead of per transaction.
• Nuvei (NUV-EP1-PSE): Add support for the new payment method PSE. PSE (Pagos Seguros en Línea) is a popular real-time online bank transfer payment method in Colombia that allows users to pay directly from their bank accounts.
• Worldpay (WOR-EP1-KLAPN): Use a default Order Line Item if none is provided, to meet mandatory requirements by Worldpay for Klarna.

Added​

• Digit Secure (DS-EP1-T2P): New push adapter with payment method Tap2Pay.

Fixed​

• Cybersource (CYS): Fix parameter typo from extraData.reconciliationId to extraData.reconciliationID (captialize D in ID).
• KakaoPay (KAKAO-EP1-KAKAO): Fix incorrect mapping of error responses.
• KCP Mobile (KCPMO): Fix issue with settlement handling for refund transactions.
• KCP PC (KCPPC): Fix issue with settlement handling for refund transactions.
• Simulator: Fix issue where payment.js did not work with the Simulator adapter.

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.