Skip to main content

19 posts tagged with "Braintree"

View All Tags

Gateway — v26.5

Gateway Features

Changed

  • Connector Settings: Add bracket notation for the connector setting Field Expression Operation for the target field extraData to allow dashes in the key name.
  • Network Tokenization: Add an additional network token configuration to the existing setting to allow creating network tokens when processing subsequent transactions.

Fixed

  • Network Tokenization: Fix an issue where disabling network token processing also disabled network token creation.
  • Transaction Details: Fix a bug where transaction logs are not properly formatted.
  • Transaction Processing: Fix automatic capture to also work for failover transactions.
  • UI: Fix the customer profile list view showing a wrong total number.
  • Virtual Terminal: Add missing translation in the Pay-By-Link UI.

Gateway Adapters

Changed

  • Adyen (ADY): Add handling of Merchant Advice Code from callback notifications.
  • Braintree (BRA-EP1-SWI): Add support for Swish, a Swedish mobile payment method that allows customers to make real-time payments using their phone number and banking app.
  • checkout.com (CHE-EP2-BIZ): Add the payment ID in the callback notification as psp:bizumPaymentId.
  • dLocal (DLO-EP1): Add a new optional configuration setting which allows sending a custom X-Dlocal-Payment-Source header.
  • eMerchantPay (EME-EP3-CC): Add support to automatically migrate existing recurring card subscriptions from the legacy platform to the Genesis platform without requiring cardholders to re-register.

Added

  • NaverPay (NAV-EP1): NaverPay is a South Korean digital wallet and online payment platform by Naver Corporation. It enables users to make seamless payments across e-commerce sites, apps, and offline merchants. The platform offers secure transactions, loyalty rewards, and easy integration for businesses.

Fixed

  • KCP PC (KCPPC): Add a temporary configuration setting which should fix issues with refunds.
  • PayPal Complete Payments - PPCP (PPCP-EP1-PPE): Fix an issue with the wallet reference handling.
  • Redsys (RED-EP2-BIAPI): Fix an issue where the authCode is not included in the callback notification.

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

Gateway Features

Changed

  • Transaction Details: Enable merchant users to view the complete transaction tree for a transaction on the Transaction Details page.

Added

  • Connector Settings: Add a new connector setting Connector custom variables which allows defining custom parameters which can be accessed on the Hosted Payment Page.

Gateway Adapters

Changed

  • Adyen (ADY): Update documentation to include AdyenCheckoutPci for the merchantAdviceCode mapping.
  • Braintree (BRA-EP1-SAT): Add support for the new payment method Satispay. Satispay is a popular Italian mobile e-wallet that allows customers to pay securely online directly from their linked bank accounts using a smartphone app.
  • dLocal (DLO-EP1): Add support for the new withholding tax column (WHT) in settlement files.
  • JPMorganChase (CHA):
    • Update amount fields to use raw, non-aggregated values.
    • Remove chargeback adjustments from settlement reports.
  • PayU (PAU-EP1): Add support for Payout Report settlement retrieval with the new Report Type setting.

Fixed

  • 2C2P (2C2P-EP1): Fix settlement retrieval to prevent duplicates.
  • Adyen (ADY-EP3-RIV): Fix missing customer data.
  • HDFC CCAvenue (CCAV):
    • Fix response handling.
    • Fix refunds for captures.
  • Klarna (KLW): Fix VAT and fee calculations for settlements.
  • Paymob (PMO):
    • Add handling to properly cancel transactions when they are abandoned by the user.
    • Fix error mapping 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 — v26.1

Gateway Features

Changed

  • Connector Settings: Extend the connector setting Hooks: Transaction Success for Capture transactions.
  • Risk Profile: Extend Forter risk engine to support risk assessment for alternative payment methods (APMs).
  • Risk Profile: Extend Forter risk engine to support additional attributes used for risk assessment.

Added

  • Connector Settings: New connector setting Postback: Don't send if Chargeback has no reason.

Fixed

  • Documentation: Fix missing customerProfileData.paymentToken in the exported transaction OpenAPI specification.

Gateway Adapters

Changed

  • Adyen (ADY-EP1-CC): Update documentation to include the merchantAdviceCode.
  • American Express (AMX): Add a new settlement setting skipNegativeNetSettlement to only map the net settlement amount if the value is positive.
  • Braintree (BRA): Allow configuring the Braintree SDK version via the sdkVersion parameter passed in the options (PayPal, Venmo and local payment methods).

Added

  • GoCardless (GOC-EP1): Add a new configuration setting Enable status sync to additionally queue a transaction status retrieval.

Fixed

  • Adyen (ADY): Adjust the settlement handling to identify the correct batch independent from the filename.

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

API

Changed

Fixed

  • Pay-by-Link API: Fixed an issue that would prevent a pay-by-link transaction from being canceled if a failover occurred for the transaction.
  • Push API: Fixed an issue that would cause a type error if an empty body request was submitted in a Push API request.
  • Transaction API: Fixed an issue where invalid 3DS values (browserColorDepth, browserTimezone) sent to the API in transaction data would cause an error. These invalid values are now ignored.

Features

Changed

  • Connector Settings: The "Postback: Include 3DS Data" connector setting is now also available in the global settings.
  • Post Processing Jobs: Optimized the process of collecting transactions in post-processing jobs.
  • UI Navigation: Improved the parent tenant selection when creating a new tenant. By default, the current tenant is set as the parent tenant and the drop-down is now searchable.
  • UI Navigation: Updated risk logs so that they are loaded asynchronously. This improves the initial load time for the transaction details view. Risk data is now only loaded when expanding the view.

Added

  • Connector Configuration: Added audit logs for the "Additional Configs" in the connector view.

Fixed

  • Audit Log: Fixed an issue that would cause an error when accessing the audit log if the corresponding merchant cannot be found when checking access permissions.
  • Fee Management: Fixed an issue that would cause an error when changing the mapping to a different fee entity. The mapping for the old fee entity is now removed, and the mapping is set to the new fee entity.
  • Post Processing Setting: Fixed an issue with the "Create unknown transaction on connector with GUID" option for settlements that prevented unknown transactions in a settlement file from being added to the platform.
  • Provider: Fixed an issue that would occur when saving a connector configuration. Previously configured connectors that were assigned to the same provider were removed when the configuration was saved, with only the new configuration linked to the provider.
  • Provider Settlements and Reconciliation: Fixed an issue that would cause an error when trying to sort missing reconciliation data by merchant.
  • Risk Profile: Fixed an issue where saving a risk rule without entering parameter values would result in a type error.
  • Risk Profile: Fixed an issue that would cause an error when opening risk rules if the risk rule set ID referenced a risk rule set that does not exist. A 404 error is now displayed instead.
  • Transaction Processing: Fixed an issue caused by the platform attempting to collect 3DS information for Apple Pay transactions. The system now checks whether a transaction uses Apple Pay before collecting additional 3DS information.
  • UI Navigation: The loading page displayed for the collectMissing3DSecureData connector configuration was only displayed in English. The page is now displayed in the language of the transaction where available, with English as the fallback language.

Adapters

Changed

  • American Express (AMX-EP1-AMX): Added a new gateway connector configuration option, "Force System Generated STAN". This option can be used to force the system trace audit number (stan) to be generated by the IXOPAY platform and stored in the additionalId1 field. The following options are available to determine the format of the STAN:
    • "Yes - Uppercase characters only"
    • "Yes - Upper- and lowercase characters".
  • Banca Intesa (BAI-EP1): If the PSP includes the TRACEID in a transaction response, it is now included in the postback.
  • Braintree (BRA-EP1-BLI): Added support for partial refunds for the Blik non-redirect payment method.
  • Braintree (BRA-EP1-PPE): Added support for line items and a corresponding option, includeLineItems has been added to the connector configuration.
  • dLocal (DLO-EP1-CC): The merchantTransactionId is now passed to the vault, in order to pass it on to the PSP in refund requests.
  • HypYaad (HYP): Removed the mapping of payment references in settlement files, as this could lead to a single settlement file being split into multiple settlements.
  • Mastercard Payment Gateway Services (MPG, BAMI): Added support for the scheme transaction ID.
  • Nexi Group (NETS-EP1): Added support for specifying the language in the checkout payload for transactions. This ensures that the language field is included in the payload if it is included in the transaction's extra data.
  • PayPal (PPA-EP1-PPE): Added the isFinalCapture flag for capture transactions. If set to true, the capture is marked as final on the PayPal side and no further captures are possible.
  • Simulator: Added support for incremental authorization for simulated credit card transactions.

Added

  • WavePay (WAV): The WavePay push adapter allows cash collection payments to be pushed to the IXOPAY platform to ensure that these transactions are also available within the system.

Fixed

  • Afterpay (AFT): Fixed an issue with retrieving the minimum/maximum price, caused by a missing interface.
  • American Express (AMX-EP1-AMX): Fixed an issue that would cause an error if settlement files are not formatted correctly.
  • Braintree (BRA): If rows in a settlement file did not include a settlement date, the settlement date was previously taken from the first value found in the "Settlement Date" column of the file. However, this could result in the settlement date being incorrect. The behavior has therefore been changed to set the settlement date to the transaction's disbursement date instead.
  • Braintree (BRA-EP1-PPE): The merchantAccountId is now only passed to Braintree's JavaScript SDK if a value is present.
  • iyzico (IYZ):
    • Fixed an issue with that would cause the batch number to be set to the entire file name of the settlement file, rather than the initial numerical portion of the file name. This was caused by empty rows in the settlement file.
    • Fixed an issue that would cause some settlement files to be parsed incorrectly.
  • Khipu (KHI): Fixed an issue with retrieving the bank list, caused by a missing interface.
  • Klarna (KLW): Fixed an issue that would result in the error "Invalid Response" being returned for transaction without a body. An empty body is now handled correctly, with the HTTP error code being checked prior to parsing the response.
  • Mashreq (MASH-EP01): Fixed an issue where the status of successful transactions was not set correctly due to the status in the response not being formatted as expected.
  • Payabl (P21): Fixed an issue caused by the error code parameter being evaluated incorrectly.
  • Paymee (PAYME-EP1-CCRD): Fixed an issue where refund amounts would be sent with a varying number of decimal places, which could sometimes lead to errors. Refund amounts are now formatted consistently.
  • Trustly (TRU): Fixed an issue that would cause a generic payment error if the private key required to generate the signature was missing. The system now checks for its presence.

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

API

Changed

  • payment.js: Updated the version of jQuery used in payment.js to 3.7.1.

Added

  • BI Data Source: Introduced BI Data Source API v2 built on OpenSearch for improved performance and functionality.

Features

Changed

  • Job Configuration: A new column has been added to the "Write customized Settlement CSV" export step, relatedFirstTransactionUuid.

Added

  • Audit Log: Audit logs are now available for providers. These logs include changes to the provider ID, data fetcher and configuration changes.

Fixed

  • Callback: Fixed an issue where notifications for partial refunds were sometimes mapped to the wrong refund transaction.
  • Post Processing Jobs: The "Write customized Settlement CSV" job step included two columns that accessed the UUID of the related transaction (referenceTxUuid and referenceUuid). referenceTxUuid has therefore been removed.
  • Post Processing Jobs: Fixed an issue that would cause an error if no provider was entered in a connector.
  • Provider Settlements and Reconciliation: When processing a settlement file, the meta-connector for a transaction is now set correctly if a meta-connector is used by the related transaction.
  • Provider Settlements and Reconciliation: Fixed an issue that would occur when creating new transactions from a settlement.
  • Provider Settlements and Reconciliation: Fixed an issue caused by restricting the allowed ports in the SFTP receiver.
  • Virtual Terminal: Fixed an issue that could occur if surcharge and GST fee calculation permissions were granted, but only surcharges were configured in the virtual terminal.

Adapters

Changed

  • Braintree (BRA-EP1): The merchant account ID has been added to the configuration used in the setup process to improve the integration. This ensures that transactions are correctly associated with the relevant merchant account.
  • Klarna (KLW-EP1-APM): Added support for the following countries:
    • Czechia
    • France
    • Greece
    • Hungary
    • Ireland
    • Italy
    • Poland
    • Portugal
    • Slovakia
    • Romania
    • Spain.
  • PXP (PXP-EP1):
    • Added support for the Aircash and Aircash Abon payment methods.
    • Added support for payout with redirect.
  • Simulator: Updated the documentation to cover overriding the outcome.

Fixed

  • Alignet (ALI-EP01-VIS): The phoneCode and phoneSubscriber fields are no longer mandatory.
  • Klarna (KLW-EP1):
    • Fixed an issue in the documentation regarding the shipping email and total discount amount. customer.shippingEmail has been corrected to customer.extraData.shippingEmail and items.item.totalDiscountAmount has been changed to items.item.extraData.totalDiscountAmount.
    • Fixed an error that would occur if a request timed out. This was caused by the empty response not being handled correctly.
  • Mashreq (MASH): Fixed an error caused by unknown transactions in the postback.
  • Sepa Express (SEP-EP3): Fixed an issue that would cause an error if the connectorId is missing when creating a mandate. The system now checks that this required value is present.
  • Worldline (ING): The SFTP password is no longer mandatory, as the setup is switching over to using a private key.

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.