12 posts tagged with "Job Configuration"

Gateway Features​

Added​

• BI Data Source: Improve the management of BDS settings by allowing the definition of default profiles at the Merchant and Connector levels for more consistent and simplified configurations.
• Job Configuration: Add support for the customerProfileIdentification and customerProfileGuid fields in export strategies (CSV, XLSX, XLSX v2).
• Job Configuration: Add a new line item grouping card Country (buyer Country as a fallback) for the Aggregate Transaction Values To Job Line Items strategy.

Fixed​

• Audit Log: Fix Audit Log Export which sometimes produced duplicate or incomplete export results.
• Risk Profile: Adjust Forter risk engine to validate ECI values to avoid formatting errors.
• Transaction Details: Fix Resend postback functionality.
• Transaction Processing: Add missing support for Auto-Capture for failover transactions.
• UI Navigation: Fix an issue in the customer profile view when loading a large number of profiles.

Gateway Adapters​

Changed​

• Stripe (STRV2): Add support to match transactions with a latest_charge for post processing purposes.

Added​

• Kueski (KUE-EP1-KP): Kueski is a leading provider of consumer credit in Mexico, enabling flexible "Buy Now, Pay Later" installment-based payments for customers without traditional credit cards. The new adapter supports the Kueski Pay payment method for Debit and Refund transaction types.

Fixed​

• Adyen (ADY): Fix handling of settlement files with unexpected file names.
• Dimoco (DIM): Fix reconciliation parsing of AUT/TRX fields and fees.
• Redsys (RED-EP2-BIZ): Improve error handling.

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​

• 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.
• Dimoco (DIM): Add a new configuration option to select between the old and new Settlement and Reconciliation retrieval logic. By default, the old logic is used.
• 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.
• 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​

Added​

• Account Updater: Add a configurable setting to specify the update interval for expired cards. Requires the merchant.account-updater.custom-interval permission.
• Connector Settings: Add a new connector setting to disable network token processing.
• Job Configuration: Add an option to skip the SFTP upload when no matching file is found for the Upload document to SFTP server export step.
• Multi-method connector: Add a new setting to display all payment methods for transactions with withRegister=true, regardless of whether they support recurring payments. If the selected payment method does not support recurring payments, the withRegister flag will be set to false. For customer profiles, the payment instrument will not be stored in that case.
• Virtual Terminal: Add support for split transactions in the Virtual Terminal.

Removed​

• Network Tokenization: Remove transaction indicator requirement check for subsequent network token transactions.

Fixed​

• Transaction Processing: Fix an edge case where the transaction token is not properly stored.

Gateway Adapters​

Changed​

• American Express (AMX-EP1-AMX): Update the settlement parser to support the new Global Raw Data Reconciliation File (GRRCN) version 4.01 (up from 3.01).
• PayU (PAU-E01-CC):
  • Add support for installments.
  • Enable recurring transactions.
• PayU (PAU-E01-PAE): Add a default expiration date of 1 day.

Fixed​

• dLocal (DLO): Fix the private key field in the provider settlement configuration.
• GoCardless (GOC-EP1-BT): Fix handling of the transaction status in the mandate flow.
• PayPal Complete Payments - PPCP (PPCP-EP1): Add support for additional transaction update callbacks.
• Worldline (ING-EP5): Fix parsing of error codes and error messages.

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​

• Job Configuration: Fix a bug in the post-processing job configuration where endpoint URL validation in the Send document to endpoint exporting configuration incorrectly restricted URL paths to lowercase only.

Gateway Adapters​

Changed​

• KCP Mobile, KCP PC (KCPMO-EP1, KCPPC-EP01): Add extra data to callback and API response, including card acquirer code (extraData.acqu_cd), card issuer code (extraData.card_cd), payment method (extraData.pay_method), truncated PAN (extraData.card_no), and bank code (extraData.bank_code).
• PayPal Complete Payments - PPCP (PPCP-EP1): Add chargeback protection details to API response, including seller protection status (extraData.seller_protection_status), dispute categories (extraData.seller_protection_dispute_categories), and PayPal account status (extraData.paypal_account_status).
• Stripe (STRV2): Add support for account funding transactions (AFT).
• Worldpay (WOR-EP1-CC): Add documentation about the extraData.refundAuthorisationReference parameter returned in callbacks.

Fixed​

• PXP (PXP-EP1-INST): Fix a typo in an error message.
• Worldline (ING-EP1, ING-EP2, ING-EP3, ING-EP4, ING-EP7): Fix chargeback handling in the settlement and reconciliation parser.

API v2​

Added​

• APIv2’s NetworkToken endpoints now return an error if multiple Network Tokens exist for a single token, requiring the new tokenReferenceId parameter to specify which one to use.

Payment Services v2​

Added​

• Add Merchant Advice and Brand Auth Response code mappings to AdyenDirect, FirstDataIPG, and Orbital gateways for additional insights on how to handle failed transactions.

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.