Skip to main content

8 posts tagged with "Connector Configuration"

View All Tags

Gateway — v25.9

Gateway Features

Changed

  • Transaction Details: Extend the Create Manual Chargeback and Create Manual Chargeback Reversal action to allow setting the settlement amount, settlement currency and settlement date.

Added

  • Transaction Details: Add support to manually create a second chargeback.

Fixed

  • Connector Configuration: Fix an issue for the connector setting Accept postbacks from other connectors where postbacks were processed through the wrong connector.
  • Provider Settlements and Reconciliation: Fix an issue handling settlements for transactions sharing the same ARN.
  • Transaction Details: Fix incorrect status display for subsequent transactions on the transaction detail page.

Gateway Adapters

Changed

  • Adyen (ADY-EP3-PAYPA): Add support for the new payment method PayPay. PayPay is a Japanese e-wallet allowing customers to either pay directly in the app or by scanning a QR code.
  • Adyen (ADY-EP4-CC): Add support for Refund and Payout.
  • DPO Pay (PAYGA-PYGT-CC): Add status retrieval for transaction communication errors (previously only for timeouts).
  • PPRO (PPR-EP1-TRU): Map the customer.email parameter to PPRO's useremail request parameter.
  • Redsys (RED-EP2): Add a new configuration to enable or disable sending Merchant Card-on-File transaction indicators for register transactions (DS_MERCHANT_COF_TYPE = R, DS_MERCHANT_COF_INI = S).
  • Worldline (ING-EP2-IDE): Add documentation for the payment method iDeal.

Fixed

  • American Express (AMX-EP1): Fix chargeback settlement amounts where wrongly saved negative values were leading to conflicts.
  • PayU (PAU-E01-MAS): Fix an issue when using customer profile tokens for subsequent transactions.
  • PPRO (PPR): Update the postback validation to support SHA-256 hashing.

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, Portal — v25.5

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.

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

Gateway — v24.16

API

Added

  • Provisioning API: Added processing:copy-customer-data-from-customer-profile-transaction to the connector settings.

Features

Changed

  • User Management:
    • Removed deprecated ACL abilities connector.WorldlineOgone.PostFinanceCard and connector.WorldlineOgone.PostFinanceEFinance.
    • Migrated existing deprecated ACL abilities to connector.IngenicoDirect.PostFinancePay.

Added

  • Connector Configuration: Add new connector setting Customer Data: Copy from customer profile transaction. If activated the shopper's information is added from the transaction that was used to create a customer profile.

Fixed

  • Job Configuration: Fixed an issue that could occur when saving Global Job Schedules.
  • Post Processing Jobs: Fixed the post-processing filter Transaction is not referenced in any job of this Job Type, ensuring it now correctly picks up transactions already collected by other job types.
  • Post Processing Jobs: Fixed the bug where the default state for newly created job schedules would be scheduled instead of Manual trigger only.
  • Transaction List: Fixed the advanced search to also filter for the meta_connector_guid when searching for transactions of a connector.
  • Transaction List: Fixed handling operators IS_EMPTY and IS_NOT_EMPTY for the advanced search.

Adapters

Changed

  • dLocal (DLO): Added support for settlement handling.
  • Klarna (KLW): Updated and restructured the documentation according to our latest guidelines.
  • PayPal Complete Payments - PPCP (PPCP-EP1-CC): Added support for the PayPal Advanced Credit Cards and Debit Card (ACDC) method.
  • PayTabs (PAYT-EP01-CCRD): Added support for the redirect credit-card payment method.
  • PXP (PXP-EP1-INST): Added support for Discover credit cards.
  • Straight2Bank Pay (STRAI): Added the configuration option daysOffset to delay data fetching a certain number of days.
  • Worldpay (WOR-EP1): Added support for chargeback handling through webhooks.

Fixed

  • Adyen (ADY-EP1, ADY-EP2, ADY-EP3): Fixes handling of second chargebacks for Adyen settlements.
  • Alipay - Ant Group (ANT-EP1-ALI): Limit retries of failed transactions to three attempts.
  • Global Payments (GBP): Fixed specifying the settlement amount.
  • PAYONE (PASIX): Fixed handling of negative fee amounts in settlements for interchange fees of refunded transactions.
  • PXP (PXP-EP1-INST): Fixed incorrectly disabled partial capture, partial void, and incremental authorization.

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.