Skip to main content

13 posts tagged with "Connector Settings"

View All Tags

Gateway — v25.8

Gateway API

Changed

  • Transaction API: Update API validation for the browserTimezone field in 3DS data to accept values prefixed with a plus sign (e.g., "+0300"), which were previously rejected, and to enforce a maximum string length of 4 characters for this field.

Added

  • Customer profiles API: Add attachPaymentInstrument and detachPaymentInstrument API endpoints to customer profiles, allowing users to attach or detach payment instruments using profile identifiers (GUID or customer identification) and a transaction UUID.

Gateway Features

Added

  • Connector Settings: Add a new connector setting Disable Refund After Chargeback, which controls whether the refund option is available for transactions that have undergone a chargeback.

Gateway Adapters

Changed

  • Adyen (ADY-EP4-CC): Add support for preauthorize and capture transactions.
  • checkout.com (CHE-EP2-BIZ): Add support for the new payment method Bizum. Bizum is a fast and secure mobile payment method widely used in Spain.
  • dLocal (DLO-EP1-SINMO): Add support for the new payment method Sinpe Móvil. SINPE Móvil in Costa Rica facilitates money transfers through SMS, allowing users to send funds to another mobile phone number without needing the recipient’s bank account information.
  • PAYONE (PASIX-EP1): Add documentation for the extraData.avsCheck field, which is used to enable Address Verification System (AVS) checks.
  • Worldline (ING-EP2-IDE): Add support for the new payment method iDeal. iDEAL is an online payment method that enables consumers to pay online through their own bank. Payments are made via bank app or online banking.
  • Worldpay (WOR-EP1-KLAPN): Update documentation to specify that item.totalAmount is a required field for the payment method Klarna.

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

Gateway Features

Added

  • BIN Lookup: Add the BIN segment to the transaction details view in the admin and merchant portals.
  • Connector Settings: Add the Copy Description to Chargeback Reversal connector setting. When enabled, the description from the original transaction will be copied to the chargeback reversal.
  • Connector Settings: Add the Copy Merchant Meta Data to Chargeback and Copy Merchant Meta Data to Chargeback Reversal connector settings. These settings enable the copying of merchant metadata to newly created chargebacks or chargeback reversals initiated through Settlements or Reconciliations.
  • Transaction Processing: Add Japanese translations for the loading screen that appears after a customer submits the payment or 3DS form for transactions requiring additional processing time.

Gateway Adapters

Changed

  • checkout.com (CHE-EP2): Add documentation for the extraData.recipientDateOfBirth and extraData.senderDateOfBirth parameters in the AFT section of the connector documentation.
  • Nexi Group (NETS-EP2): Improve the description of error messages for the connector.
  • Paymob (PMO-EP2-CCRD): Add the bank_installments_integration_id and bank_installments_enabled connector settings. When both settings are configured, the bank_installments_integration_id will be included in the PSP payload, allowing users to select installments as a payment option in the payment modal for credit card redirects.
  • Worldline (ING-EP2, ING-EP7): Add the shouldBeFinishedWhenCapturedSofort connector setting. When enabled, Sofort debit transactions will be marked as successful when the status changes to captured.

Fixed

  • DPO Pay (PAYGA-PYGT): Fix an issue where the transaction status in the adpater could be incorrect after a timeout by the PSP. The platform now polls the status API to ensure the correct transaction status is set.
  • Redsys (RED-EP2-BIAPI): Maintain and update the payment service provider's transaction ID from the initial transaction in subsequent 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 — v25.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.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.15

API

Fixed

  • Provisioning API: Resolved an error in the Provisioning API by adding null checks when building response objects for meta connectors without a default connector.
  • Push API: Fixed handling of request bodies with invalid JSON.

Features

Changed

  • Customer Profiles: Made the action column in the customer profile payment instruments table non-sortable.
  • Transaction List: Increased the number of displayed connectors in the advanced search form from 100 to 700.

Added

  • Post Processing Jobs: Added the ability to export transaction extra data in post-processing export strategies, including "Write customized Settlement CSV", "Export Transactions to XLSX (Version 2)", "Export Transactions to XLSX", and "Export Transactions to CSV". Also, added "key" and "default" column configurations to "Export Transactions to XLSX (Version 2)", "Export Transactions to XLSX", and "Export Transactions to CSV".

Fixed

  • Account Updater: Improved the account updater to consider BIN lookup results alongside the card type for more accurate processing.
  • Account Updater: Fixed an issue in the Account Updater that caused cards to appear as updated twice in the batch for clients.
  • Connector Settings: Fixed a bug that caused the connector settings "Transactions: Expire automatically after (x) minutes" and "Expires pending transactions after given minutes" to not work when added as Global Settings.
  • Customer Profiles: Use the correct customer profile container for meta connectors.
  • Dashboard: Fixed an issue where the pivot table couldn’t resolve the connector list, causing multiple selections to show as ‘n/a’.
  • Dashboard: Fixed a dashboard issue where GUIDs were displayed instead of merchant names.
  • Hosted Payment Pages: Removed async from Google Pay JS on hosted payment pages to enable synchronous loading, ensuring the Google Pay button displays reliably.
  • Transaction List: Updated transaction list links to ensure they work correctly by including a default status, preventing 404 errors.
  • Virtual Terminal: Fixed issues in the Virtual Terminal for direct debit transactions by preventing mandate date validation when the field is empty and correcting format validation to display proper error messages instead of "unknown error".

Adapters

Changed

  • Klarna (KLW-EP1): Added a connector setting "treat the BACK status from klarna as CANCELLED".
  • Mashreq (MASH-EP01): Added support for debit auto-capture.
  • PAYONE (PASIX): Add new mappings for settlements:
    • Markup fee (condCode 701)
    • Dispute fee (condCode 55).
  • PXP (PXP-EP1-INST): Added support for the in-store card deposit payment method.
  • Sepa Express (SEP-EP3-SEP): Added support for settlement handling.
  • Worldline (ING-EP2): Always store the adapter transaction identifier if present to properly handle subsequent transactions.

Fixed

  • American Express (AMX-EP1-AMX): Fixed system trace audit number (STAN) issue by using a modulus operation on the transaction ID to ensure it fits within base36 encoding limits.
  • iyzico (IYZ): Fixed settlement handling for Iyzico to correctly parse the batch number for all settlement objects.
  • Spreedly (SPR-EP1-CC): Fixed date parsing to correctly handle microseconds included by the PSP.
  • Transbank (TRANS-TSB1): Fixed handling of empty responses.

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.