Skip to main content

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 — v.25.3

Gateway API

Added

  • Transaction API: Add the includeTracing parameter for Status API and Transaction API for debit & preauthorize requests, enabling transaction routing and cascading details in the Status API response and Transaction API callbacks.

Gateway Features

Changed

  • Audit Log: Update the User-Management report to reflect the selected user type (userType), include user descriptions (description), the merchant column (merchant) for relevant user types.

Added

  • Connector Settings: Add a new connector setting: Expire transaction with a given status after given minutes, allowing configuration of multiple statuses and expiration times. This replaces the need for separate settings for pending and automatic transaction expirations.
  • Transaction Details:
    • Allow adding custom data values to manual refunds and captures, configurable in tenant settings.
    • Introduce a new permission, frontend.transaction.add-extradata-to-manual-capture-refund, to manage access to this feature.
  • Transaction List: Restore the Copy from Standard Filter button in the advanced search.
  • User Management: Add a new field, Description, to the base data for all users, visible in the Create New User, Edit User, and User Overview views.

Removed

  • Connector Settings: Deprecate the connector settings Expires pending transactions after given minutes and Transactions: Expire automatically after (x) minutes, as their functionality is now covered by the new setting that supports expiring transactions based on specific statuses.

Gateway Adapters

Changed

  • EquensWorldline (EQW): Add ARN (Acquirer Reference Number) to settlement when parsing reconciliations.
  • JPMorganChase (CHA-EP2-CC): Improve documentation for new extraData fields (extraData["card.cardVerificationResult"], extraData["card.cardVerificationResultCode"], and extraData["card.paymentAccountReference"]).

Fixed

  • dLocal (DLO-EP1): Correct the payout country restrictions link in the adapter documentation.

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

Gateway API

Changed

  • Transaction API: Extend the callbackUrl length for refund requests (Refund) from 255 to 4096 characters.

Added

  • Customer profiles API: Add the fields associatedTokenType and networkTokenStatus to the /api/v3/customerProfiles/:apiKey/getProfile response for payment instruments of type card.

Gateway Features

Added

  • Transaction Details: Add an Associated Tokens column (Network Token with Status, Google Pay Token, and Apple Pay Token) to the Customer Profile credit card payment instruments in the admin and merchant views.
  • User Management: Add a new acl.roles.show permission for a read-only view of roles.

Fixed

  • Transaction List: Fix the advanced transaction list filter for Retrieval Reference Number (RRN).

Gateway Adapters

Changed

  • EPG Financial Services Limited (EPG-EP01): Allow passing the extraData.ext_client_id parameter for Premium Partner solution participants to link Paylado accounts with player accounts.
  • JPMorganChase (CHA): Add support for settlement handling.
  • JPMorganChase (CHA-EP2-CC): Adds extraData["card.cardVerificationResult"], extraData["card.cardVerificationResultCode"], and extraData["card.paymentAccountReference"] to the response and callback payloads.
  • KakaoPay (KAKAO): Updated default behavior to fetch settlement files from yesterday instead of looking back 30 days on the first fetch.
  • PayPal (PPA): Map actual-net-settlement-amount settlement line item for reconciliation.
  • Redsys (RED-EP2-BIZ): Add support for the new payment method Bizum. Bizum is a service promoted by Spanish banks that connects customers' current bank accounts by linking them to their cell phone number.
  • Worldpay (WOR): Change the chargeback creation date from the webhook receipt date to the date_post provided in the postback request.
  • Worldpay (WOR-EP1-CC): Add a recommendation to the adapter documentation to enable the connector setting Postback: Send After Each Notification for online refund notifications.

Added

  • Paymob (PMO-EP2-CCRD): Add the Paymob adapter with support for redirect credit card payments. Paymob (formerly known as WeAccept) is a payment service provider and payment aggregator that empowers businesses to get paid wherever their customers are.

Fixed

  • KCP Mobile (KCPMO-EP1): Fix encoding issue on the Hosted Payment Page.
  • Mashreq (MASH): Fixed an issue with postback sharing where transactions were not processed correctly when postback sharing was enabled via the setting Accept postbacks from other connectors (list GUIDs comma-separated).
  • PXP (PXP-EP1-INST): Add mapping for payment state 15 to “Transaction Declined” error.

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 v2, Gateway, Payment Services v2 — v.25.1

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.

Gateway — v.25.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.