22 posts tagged with "Provider Settlements and Reconciliation"

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.

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.

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.
• Simulator: Fix a configuration issue for Simulator settlement handling.

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