Skip to main content

20 posts tagged with "Provider Settlements and Reconciliation"

View All Tags

Gateway — v25.13

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

  • DigitSecure (DS-EP1): New push adapter with payment method TapToPay.

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.

Gateway, Portal — v25.12

Gateway API

Fixed

  • Batch-upload API: Resolve a limitation that previously prevented the processing of batch files with more than ~50 transactions.

Gateway Features

Changed

  • Transaction Details: Improve clarity for transaction fee names.
  • Transaction Details: Allow manual chargebacks, second chargebacks, and chargeback reversals to be processed for an amount greater than the original transaction.

Added

  • Transaction Details: Add the option to use a custom merchant transaction ID for manual Voids and Refunds.

Fixed

  • Hosted Payment Pages: Fix possible race condition when loading JavaScript on the Hosted Payment Pages in certain scenarios.
  • Provider Settlements and Reconciliation: Fix a minor bug in the settlement process when handling chargeback reason codes.
  • Simulator: Fix a configuration issue for Simulator settlement handling.

Gateway Adapters

Changed

  • checkout.com (CHE): Minor improvements to reliability for callback handling.

Added

  • Amazon Payment Services (AMAZO-EP1-KNET, AMAZO-EP2-KNET): Amazon Payment Services is a leading payment provider in the Middle East, offering secure and localized payment solutions. The new adapter supports the payment method KNET for transaction types Debit and Refund. KNET is a popular debit-based payment network in Kuwait, enabling real-time bank transfers for online purchases.

Fixed

  • DPO Pay (PAYGA-PYGT-CC): Fix issue where transaction status was not properly retrieved after communication errors.
  • Nuvei (NUV): Fix issue causing the reserve to be incorrectly saved as a transactional fee.

Portal

Changed

  • Proxy Tokenization (Deployed in release v25.9):
    • Support special characters in alias
      • Dash and underscore supported only
    • Bug fix - Profile details to display ID number if optional name is empty
    • Profile & Key name auto save
      • Auto save optional name upon click outside of field
    • Account Logging
      • Profile, Key & Alias event tracking
        • Create
        • Edit
        • Delete

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, Portal — v25.5

Gateway Features

Changed

  • Provider Settlements and Reconciliation: Add the ARN in chargeback transactions created following receipt from a Settlement Handler.

Added

  • Connector Configuration: Add descriptions for connector settings and configurations where available, providing additional context.
  • JPMCommercePlatformPci Post-Processing: Add support for new sale merchant types, a new CSV file format, and calculations for Total Fees, Total Sales, Total Refund, Total Chargeback Amount, and Net Payment Amount.
  • Meta connector: Add new routing rule, Check Credit Card BIN Is Prepaid, that allows you to route transactions based on whether a credit card is prepaid, determined by its BIN entry.
  • Meta connector: Add new routing rule, Credit Card BIN Is Reloadable, that enables transaction routing based on whether a credit card is reloadable, as determined by its BIN entry.

Fixed

  • Post Processing Jobs: Fix duplicated data being written when Post Processing job conflicts are resolved with the action Resolve Conflicts.
  • Transaction Processing: Fix the scheduling of delayed captures for failover transactions that require redirects, ensuring delayed captures are applied correctly.

Gateway Adapters

Changed

  • Adyen (ADY-EP3): Add documentation for installment capabilities to the connector's adapter documentation.

Fixed

  • Paymob (PMO-EP2): Fix response parsing in the connector to handle null values.

Portal

Added

  • Proxy Tokenization Page:
    • Proxy profile name added to the details pane while in edit view. This provides confirmation of which proxy profile is being edited.
    • Ability to delete proxy profile keys. This enables users to remove/discard proxy keys created in error or no longer in use.

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

Gateway API

Fixed

  • Provisioning API: Fix an error that occurred when attempting to update merchant users with apiUserSettings configured.

Gateway Features

Changed

  • Connector Configuration: Change save message of connector configuration to display multiple validation errors simultaneously, instead of just one.
  • Risk Profile:
    • Applied cosmetic changes for consistency, including button renaming and layout adjustments.
    • Restricted Audit Log access with the Admin User Permission misc.show-public-audit-log.

Added

  • API Testing: Add a Clear CC Token button to the API Testing view to reset credit card fields without refreshing the page.
  • Risk Profile: Add a new risk rule to validate the presence of both the transaction indicator and reference scheme ID.
  • Risk Profile: Add support for BIN segments (Consumer, Business, Commercial, Government, Unknown) and add a new risk rule BIN segment of credit card is [in, not in] [list of segments] to replace the previous BIN level of credit card is [in, not in] [list of levels] rule in the future, allowing checks for specific BIN segments.

Fixed

  • Connector Settings: Fix compatibility of the Manipulation: Always set withRegister connector setting on meta-connectors with Customer Profiles to ensure payment instruments are properly stored.
  • Provider Settlements and Reconciliation: Fix an issue where the upload button remained in the uploading state after a manual file upload error.

Gateway Adapters

Changed

  • dLocal (DLO-EP1):
    • Add /options/installmentsPlan endpoint to retrieve installment plans.
    • Add extra data parameters to debit and preauthorize transactions to enable installements (extraData.installments and extraData.installments_plan_id).
    • Change required status of customer.nationalId from mandatory to optional.
  • JPMorganChase (CHA-EP2): Add support for partial void transactions.
  • KakaoPay (KAKAO-EP1): Add support for settlement and reconciliation handling.
  • Nuvei (NUV-EP1):
    • Change required status of customer.email from mandatory to optional.
    • Change sFTP retrieval to no longer require permissions to rename the file on the remote server for settlement and reconciliation handling.
  • PayPal Complete Payments - PPCP (PPCP-EP1): Add chargeback protection details to postback response, including seller protection status (extraData.seller_protection_status), dispute categories (extraData.seller_protection_dispute_categories), and PayPal account status (extraData.paypal_account_status).
  • Worldpay (WOR-EP1): Add postback handling for online refunds. Merchants will receive the Refund Authorisation Reference number in extraData.refundAuthorisationReference via postback.

Added

  • Banco Popular Dominicano (BPD-EP1): Add the Banco Popular Dominicano adapter with support for debit transactions. Banco Popular Dominicano is the first privately owned bank in the Dominican Republic and is the leader in a wide range of banking and financial services in the country. It is the principal company of Grupo Popular.

Fixed

  • Global Payments (GBP): Prevent duplicate settlement errors by using more specific settlement batch numbers.
  • JPMorganChase (CHA-EP2):
    • Fix handling of partial void followed by capture.
    • Update extraData.totalAuthAmount after partial void.
  • PayPal Complete Payments - PPCP (PPCP-EP1-PPE):
    • Enable partial capture and void capabilities for the PayPal payment method via the PayPalCompletePlatform adapter.
    • Ensure that the PayPal Partner Attribution ID is set for transactions processed through multi-method connectors.
  • PXP (PXP-EP1): Fix mapping of error code 100(77).
  • Stripe (STRV2-EP1): Use net amount instead of gross amount when parsing Line Items and Rolling Reserve for the Stripe Settlement Report.

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 — v24.20

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.