Skip to main content

10 posts tagged with "BI Data Source"

View All Tags

Gateway — v26.9

Gateway API

Changed

  • Transaction API: Add adapter name and brand to tracing data (includeTracing).

Added

  • Batch-upload API: Introduce Batch Upload API V2.
    • Support for deregister transactions.
    • A new lenient processing mode that skips invalid rows instead of aborting the batch.
    • A structured JSON result file.
    • Dedicated endpoints for status polling, result download, and batch listing.

Fixed

  • Push API: Fix an issue where the provider was not assigned to transactions.

Gateway Features

Added

  • Customer Profiles: Add the ability to exclude specific stored payment instruments on the payment selection page.
  • Meta connector: Add a new routing rule which allows routing to specific card networks.

Fixed

  • BI Data Source: Fix an issue where network token status changes were not reflected in the BI Data Source.
  • Post Processing Jobs: Fix an issue where the transaction count in the Transactions tab of a post-processing job could be lower than the actual number of transactions.

Gateway Adapters

Changed

  • Adyen (ADY-EP3-CC): Update response mapping documentation for AVS and CVV.
  • Autopay (AUTO): Add rolling reserve line items to settlements, distinguishing between deducted reserve amounts and payout amounts.
  • checkout.com (CHE-EP1-CC,CHE-EP2-CC): Add support for unreferenced refunds.
  • dLocal (DLO-EP1-CC): Add a configuration setting to set a default transaction indicator for register transactions.
  • dLocal (DLO-EP1-NETIN): Add support for the new payment method NetBanking. NetBanking is a popular bank transfer method in India that supports recurring payments, allowing customers to securely authorize a mandate for future subsequent transactions.
  • Klarna (KLW): Add a sendReferenceInCaptures configuration setting to include the transaction UUID in capture requests for reconciliation purposes.
  • PayPal (PPA): Add support for retrieving settlement reports from the sandbox environment when the connector is in test mode.
  • PPRO (PPR-EP1-EPS): Add support for reversal handling.
  • PPRO (PPR-EP1-IDE): Add support for reversal handling.
  • PPRO (PPR-EP1-TWI): Add support for the new payment method TWINT. TWINT is the leading mobile payment method in Switzerland, allowing users to complete transactions instantly either directly in the smartphone app or by scanning a QR code.

Fixed

  • Autopay (AUTO-EP1): Fix register requests in migration flows to inherit the transaction indicator from the original transaction.
  • HUA NAN COMMERCIAL BANK (HNCB-EP1-CCRD): Fix transactions failing due to a transaction reference exceeding the maximum field length.
  • Redsys (RED-EP2-BIZ): Fix an issue where payment cancellations were routed to the error URL instead of the cancel URL.

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 — v26.3

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 — v25.4

Gateway API

Changed

  • Transaction API: Modify the tracingData.transactions[].status field to use an enum with predefined status values instead of a string.

Added

  • Transaction API: Add returnData.binSegment and returnData.binRawData for returnData._TYPE of cardData in the Transaction API response.

Fixed

  • Transaction API: Fix an issue where the returnData.merchantAdviceCode (MAC) was not returned when its value was zero.

Gateway Features

Changed

  • Account Updater: Improve account updater batch processing.
  • Performance: Improve performance when using a large number of routing rules.
  • Transaction Details: Enable Apply Extra Data from initial transaction and Apply new Extra Data by default for manual refunds.

Added

  • BI Data Source: Add result_extra_data.googleCryptogramPresent to reflect 3DS authentication for Google Pay transactions.
  • Transaction Processing: Introduce the extraData.googlePayCryptogramPresent field in the Transaction API response to indicate 3DS authentication for Google Pay transactions.

Fixed

  • Network Tokenization: Fix an issue where network tokens were not deleted after failed transactions.
  • Post Processing: Fix an issue that prevented manual file uploads of MIME type application/x-ndjason.
  • Transaction Processing: Fix an issue that prevented schedules from being created in certain scenarios.

Gateway Adapters

Changed

  • Redsys (RED-EP2): Support Register transactions and add recurring functionalities for the BizumAPI payment method.

Fixed

  • PayPal (PPA): Improved settlement handling for edge cases during reconciliation.
  • PXP (PXP-EP1): Fix error mapping for specific error codes.

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

API

Added

  • Push API: Add transactionSubType to the /chargeback endpoint.

Features

Changed

  • Risk Profile: Add parameters to Count Chargebacks Risk Engine Strategy to include or exclude RDR transactions.

Added

  • Account Updater: Add connector setting Account Updater: Snooze Updates for Status Contact-Cardholder to skip future account updater runs for the response status Contact-Cardholder for up to 36 months.
  • BI Data Source: Add field subType to the BI Data Source enabling better transaction distinction and filtering of RDR transactions.
  • Dashboard: Add a filter for subType to Trend: Compare Chargeback Rate dashboard widget.
  • Post Processing Jobs: Add Transaction Type and Transaction Subtype columns to the exported email of the Send Reports to Merchants post-processing job strategy.
  • Risk Profile: Add Is Credit Card Prepaid and Is Credit Card Reloadable risk rules.
  • Transaction List: Add field subType to the Advanced Filter enabling better transaction distinction and filtering of RDR transactions.

Fixed

  • Transaction Details: Fix Load More button for transaction logs exceeding 100 entries.

Adapters

Changed

  • Bangkok Bank (BB): Add optional PGPPrivateKey and PGPKeyPassPhrase fields to the data fetcher's Extra Data, to support PGP-encrypted settlement file decryption.
  • checkout.com (CHE): Remove the requirement to send customer.bic or customer.extraData.bic fields and the requirement to perform a separate /options getIssuers call.
  • CMI (CMI): Add support for settlement handling.
  • Nuvei (NUV-EP1): Remove the requirement to send customer.email, this is now an optional field.
  • PayTabs (PAYT-EP01): Add connector config Enable iframe mode to support checkout via iFrame.
  • PPRO (PPR-EP1): Add a configuration option for alternative PPRO return mode.
  • Worldpay (WOR-EP1): Add support for chargeback notifications.

Added

  • Fiuu (FIUU-EP1): Add the Fiuu (formerly Razer Merchant Services) adapter with support for debit and refund transactions. Fiuu is Southeast Asia's leading payment gateway, enabling seamless payments for businesses and individuals.
  • JPMorganChase (CHA-EP2): Add the J.P.Morgan Commerce Platform adapter with support for debit, preauthorize, (partial) capture, (partial) refund, and recurring transactions. J.P. Morgan is a leader in financial services, offering solutions to clients in more than 100 countries with one of the most comprehensive global product platforms available.

Fixed

  • KakaoPay (KAKAO-EP1): Add extraData.paymentMethodType field with possible values MONEY or CARD.
  • KCP Mobile, KCP PC (KCPMO-EP1, KCPPC-EP01): Fix live endpoint.
  • PayPal Complete Payments - PPCP (PPCP-EP1):
    • Fix missing prepareCallEndpoint for the multi-method payment connector.
    • Ensure PPCP payment method availability in the multi-method payment connector.
  • SIA (SIA-E01): Fix setting transaction status to error on failed 3DS authentication, enabling follow-up THREEDSAUTHORIZATION2 call.

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

API

Changed

  • Status API: Exposes the acquirer reference number (ARN) via the field extraData["arn"] when it is available.
  • Transaction API: Exposes the acquirer reference number (ARN) via the field extraData["arn"] when it is available.

Fixed

  • Transaction API: Fix an issue where missing wallet data fields (walletOwner, walletReferenceId, walletOwnerFirstName, walletOwnerLastName, walletOwnerCountryCode) could cause an error. These fields are now treated as not provided.
  • Transaction API: Implement stricter currency format validation, requiring merchants to send amounts with the correct number of decimal places for each currency (e.g., EUR: 9.99 or 9.9, JPY: 5 or 5.00). If the correct format can't be provided by merchants, the tenant can be configured to round amounts commercially according to our currency definition. These settings are inherited by sub-tenants. For assistance in configuring this setting, please contact your customer success manager.

Features

Added

  • BI Data Source: Add a new data field, sub_type, for transaction subtypes related to rapid dispute resolution (RDR) in the BI data source.
  • Login: Store redirect data in the URL to ensure that after multi-tab logout and login, each tab returns to the originally requested page instead of the landing page.
  • Token Count Aggregation: Add filters to the post-processing step Calculate Token Count, allowing users to:
    1. Exclude Merchants having this Job Types scheduled
    2. Exclude Connectors having this Job Types scheduled
    3. Only Methods.

Fixed

  • Connector Configuration: Fix a bug in the transaction expiration process to ensure the Ignore Global Setting connector setting is respected whenExpire Pending Transactions or Expire Transactions is enabled.
  • Connector Configuration: Fix an issue where a valid value of 0 for the connector setting Postback Queue: Set maximum number of retries was incorrectly treated as missing or invalid. The system now properly accepts 0 as a valid input.
  • Documentation: Fixes the API authentication examples by removing the newline character that was incorrectly included in the base64-encoded concatenation of the username and password.

Adapters

Changed

  • 2C2P (2C2P-EP1-2C2PB): Update the payment channels by removing Thanachart Bank and adding the new TMBThanachart Bank following the merger with TMB Bank.
  • KCP Mobile, KCP PC (KCPMO, KCPPC): Add support for settlement handling.
  • Mercado Pago (MERPA-PROD): Adds a new header to the payment request containing the DeviceData. This allows the collection of the DeviceID when redirecting the user to the Hosted Payment Page (HPP).
  • PXP (PXP-EP1-CC): Map the field ProviderExternalID to acquirer reference number (ARN).
  • Stripe (STRV2-EP1-CC, STRV2-EP3-CC (extends STRV2-EP1-CC)): Add the ability to pass requestExtendedAuthorization as extra data to Stripe to request an authorization to be extended for up to 30 days.
  • Worldpay (WOR-EP1): Update AFT documentation.

Added

  • KakaoPay (KAKAO): Add the KakaoPay adapter with support for debit, refund and partial refund transactions. KakaoPpay is a South Korean fintech company specializing in digital payments, money transfers, and financial services.

Fixed

  • KCP Mobile (KCPMO-EP1):
    • Use Code as fallback response code if res_cd isn't available.
    • Fix an issue where the wrong value (payment method ID instead of payment method name) was sent for the pay_method field.
  • Nuvei (NUV-EP1-CC): Fixes the fail-over transaction to Nuvei by ensuring that the firstPaymentDoTransactionId is only set if the related transaction was created through Nuvei; otherwise, it is omitted to prevent rejected transactions.
  • PXP (PXP-EP1-INST): Fix wrong format of expiryMonth and expiryYear in adapter result.
  • Zona Virtual SA - Zonapagos (ZONA-EP1): Fix status retrieval handling to consider only the latest status, as recommended by the PSP.

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.