15 posts tagged with "Braintree"

API​

Fixed​

• Transaction API: Fixed an issue where adapter error codes (errors.adapterCode) were sometimes returned as a numeric value instead of as a string.

Features​

Changed​

• Connector Configuration: When adding a connector or meta-connector, the public integration key is now prefilled with a random valid value. This value can still be edited and realtime feedback is provided on whether the edited value is valid.
• Connector Settings: Ensured referenceUuid is present in all cases when the connector setting Postback/Status: include reference uuid for all subsequent transactions in postback request and status response is enabled.
• Virtual Terminal: The virtual terminal has been reworked, including the Transaction, Customer, Credit Card and Payment details sections. New permissions have been introduced to handle the new streamlined form. Some of the business logic has been reworked or extended and GST calculations are now included in the Transaction section. The type of transactions available in the virtual terminal can now also be restricted using a new tenant/connector setting. For more information, refer to the User Manual.

Added​

• Connector Settings: Added a new connector setting Postback/Status: Include captureId for debit transactions in postback request and status response if available to enable sending captureId in callback requests and status responses.

Fixed​

• BI Data Source: Fixed the recurring status for chargeback and chargeback reversal transactions in the BI data source.
• Post Processing Jobs: Fixed an issue that would cause an error if the ID for a post processing job schedule was incorrect.
• Post Processing Jobs: It is now possible to add static values to aggregated lines in CSV exports by defining a default value for the static column field.
• Provider Settlements and Reconciliation: Settlements can now be resolved using all available IDs.
• Provider Settlements and Reconciliation: When assigning a connector to a provider, it is now possible to view and select the connectors for these merchants assigned to sub-tenants.
• User Management: Fixed an issue that could result in an error when a user attempts to change their password. In such cases, users are now redirected to the login page instead.

Adapters​

Changed​

• Adyen (ADY-EP1-CC, ADY-EP3-CC): Added support for network tokenization.
• dLocal (DLO-EP1): Added an option to omit the callback_url parameter, as this removes the back button on the dLocal payment page.
• Stripe (STRV2-EP1-CC): 3DS result data from Stripe is now included in callbacks.
• Worldpay (WOR-EP1): Added a new setting, Debit waits for webhook, to postpone marking a debit transaction as successful. This setting waits for the capture event webhook notification instead of relying solely on the authorization webhook.

Added​

• Worldline (ING-EP2-MUB): Added support for the Multibanco payment method (bank transfer). Multibanco is the largest interbank network in Portugal.

Fixed​

• Adyen (ADY-EP3): Updated the API documentation to include the merchantOrderReference parameter.
• Braintree (BRA): Added support for settling chargeback reversals.
• DPO Pay (PAYGA-PYGT-CC): Updated the adapter documentation to cover new capabilities (PreAuth, Void, Capture).
• E-Comprocessing, eMerchantPay (ECP-EP1, EME-EP3-CC): Added API documentation for eMerchantPay and E-Comprocessing.
• MultiSafepay (MUL-EP1): Fixed a typo in the status used by callback handling for chargebacks.
• Nuvei (NUV-EP1): Updated the API documentation to include information on mandatory fields.
• Nuvei (NUV-EP1-CC): Fixed an issue that caused the transaction ID to be incorrectly set to IXOPAY's internal UUID until the callback is received.

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.

Features​

Changed​

• Job Configuration: Strengthened TLS verification for the target host when utilizing the Send document to endpoint post-processing step.

Added​

• Connector Settings:
  • Added a new connector setting Postback/Status: include original adapter reference id in postback request and status response to enable sending extraData["originalAdapterReferenceId"] in callback requests and status responses for all transaction types.
  • Added a new connector setting Postback/Status: include reference uuid for all subsequent transactions in postback request and status response to enable sending referenceUuid in callback requests and status responses for all transaction types. This includes transactions referenced directly via the referenceUuid field, as well as related transactions in the customerProfileData.customerProfileGuid field of the customer profile, provided the customer profile belongs to the affected merchant.

Fixed​

• Customer Profiles: Fixed an issue where manually detaching a payment instrument without deleting it from a customer profile caused unwanted behavior.
• Provider Settlements and Reconciliation: The callback URL for chargebacks initiated through settlement processing is determined automatically. If the related transaction lacks a callback URL, the transaction tree is searched for an appropriate destination.
• User Management: Extended the Include Sub-Tenants filter to include sub-tenants of sub-tenants, not just direct sub-tenants.

Adapters​

Changed​

• Adyen (ADY-EP3-MBWAY): Added support for the MB Way payment method to Adyen Checkout. MB WAY, provided by MULTIBANCO, serves as a mobile wallet within Portugal's interbank payment network.
• checkout.com (CHE-EP2-IDE): Added support for the iDEAL payment method using the checkout.com NAS platform. 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.
• Klarna (KLW-EP1):
  • Added documentation on required parameters.
  • Added fallback logic to populate essential customer fields when shipping data is missing.
• Worldline (ING-EP2): Added support for the Sofort payment method. Sofort is the predominant online banking method in countries such as Germany, Austria, Switzerland and Belgium and continues to expand its global reach.

Fixed​

• 2C2P (2C2P-EP1): Improved the handling of empty HTTP responses received from 2C2P.
• Alignet (ALI-EP01-CC):
  • Updated documentation to clarify that customer shipping address first and last name parameters are optional.
  • Included extraData from referenced transactions in follow-up transactions.
• Bitpay (BTP-EP1): Fixed cancelUrl forwarding to Bitpay and introduced logging for Bitpay invoice adapter calls.
• Braintree (BRA): Skip loading transaction data when receiving Braintree callbacks without a paymentId.
• checkout.com (CHE):
  • Fixed an issue where settlement processing failed if a previous data fetcher returned no data.
  • Updated documentation with more detailed information about extraData fields relevant to the recipient of account funding transactions.
• Sepa Express (SEP): Improved UTF-8 handling in the account holder field to handle invalid characters more effectively.
• Unzer (UNZER-EP1): Fixed an issue with handling empty responses from the PSP.
• Volt (VOL-EP1): Enhanced callback processing to immediately mark transactions as successful upon receiving a COMPLETED status callback and the successOnSettle connector setting is enabled.
• Worldline (ING-EP2): Fixed an issue with follow-up debit transactions that reference transactions based on imported IBAN tokens.

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​

Fixed​

• Batch Upload API: Fixed a number of issues with the Batch Upload API:
  • Fixed a bug that generated an incorrect output format when an error occurred.
  • Fixed an issue when querying the status of a batch request that would result in an HTML response being generated when the batch ID referenced a non-existent batch. A JSON response is now generated containing "batch not found".
  • In cases where validation errors (e.g. the merchantTransactionId is already assigned) prevents a transaction from being created, the transaction was not written to the output at all. The output now includes a line with success = false, along with an error message in the output file for every transaction that could not be created.
• Transaction API: Removed the thousands separator from the amount field in callbacks for transactions with a surcharge fee.

Features​

Changed​

• UI: The Tools section in the platform has been overhauled. The entries previously located here have been moved to more relevant parts of the platform - this includes options such as BitPay pairing and Tokenization.

Added​

• Job Configuration: Added a new feature to automatically add comments to potentially fraudulent transactions and send out emails with relevant information.

Fixed​

• Connector Settings: Fixed a minor visual issue that occurred when selecting the same connector setting twice. The setting was then displayed twice. The setting is now only displayed once.
• Post Processing Setting: Fixed an issue with sending callbacks for transactions created via settlements.
• Transaction List Filter: Fixed an issue with the filter for transactions created in test mode not being applied correctly.
• User Management: Fixed an issue where users were unable to add new merchant users unless they had the frontend.users.roles.edit permission.

Adapters​

Changed​

• Amazon Payment Services (AMAZO-EP1-CC): Added support for the new JSON settlement format.

Added​

• Alignet (ALI-EP01-CC): Alignet is a leading technology company based in Peru, specializing in solutions for secure electronic transactions. They pioneered the use of 3-D Secure in Latin America and are a key supplier of major banks in the region. The adapter supports credit card transactions.
• Braintree (BRA-EP1): Added support for the Blik payment method. Blik allows for bank transfers and covers all major Polish banks.
• PayTabs (PAYT-EP01-VALU): PayTabs is a payment processing solution specializing in seamless online transactions in areas such as the Middle East, North Africa and Southeast Asia. The adapter currently supports payments using the valU BNPL payment method in Egypt.
• Worldline (ING-EP2): Added a new endpoint as well as the option to switch between old and new endpoints in the configuration.
• Worldpay, checkout.com (CHE, WOR): Updated the API documentation for checkout.com and WorldPay WPG to include AVS and CVV responses.

Fixed​

• Adyen (ADY-EP3): Fixed an issue with missing notification verification for AdyenCheckout.
• Adyen (ADY-EP3-RIV):
  • Added support for partial captures for the Riverty payment method using Adyen Checkout.
  • The IP address field is now optional instead of mandatory when using the Riverty payment method with AdyenCheckout.
• Bitpay (BTP-EP1-CR): Fixed pairing issues with the new Bitpay connector configuration.
• Braintree (BRA-EP2): Fixed an issue with Braintree's Address Verification Service.
• checkout.com (CHE):
  • Fixed the handling of settlements for transactions with multiple partial captures.
  • Multiple fees are now supported for a single transaction in the settlement report.
• Klarna (KLW-EP1-APM): HTTP 400 responses are now mapped correctly.
• Mashreq (MASH-EP01): Added handling for the status "Awaited", which previously returned an error (due to this status not being documented by CCAvenue). The transaction is now set to pending when this status is received.
• MultiSafepay (MUL): Fixed an issue with the settlement fetcher that prevented settlements from being retrieved.
• Nuvei (NUV-EP2): Enabled support for partial captures.
• Zona Virtual SA - Zonapagos (ZONA-EP1):
  • A unique numeric value is now generated and sent to Zona Virtual as the payment ID Id_pago. This value is stored in the additionalId1 field in IXOPAY as a payment reference that is used if the payment fails.
  • Changes have been made to the mandatory fields. The following fields are no longer mandatory: merchantMetaData, extraData.idType, customer.identification.
  • Fixed the default error mapping.
  • Added mapping for the error when a payment cannot be found.

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.

Features​

Fixed​

• Transaction Details: Additional headers for callbacks including Content-Type, Accept and User-Agent are now added to the postback transaction logs in the transaction details view when the postback:send-test-plain-header or postback:send-useragent-header are set in the connector settings.
• Transaction Export: Fixed an issue with the export of transaction data for merchants with mult-merchant access.
• UI Navigation: The Croatian and Slovenian translations have been updated.

Adapters​

Changed​

• Braintree (BRA-EP2-CC): The connector configuration has been updated, see the documentation for more information.
• Braintree (BRA-EP1): The additionalId1 field is now mapped to the descriptor name instead of the descriptor URL.
• Cybersource (CYS-EP1-CC): Updated the description of auxiliary data in the documentation.
• DPO Pay (PAYGA-PYGT): The DPO Pay adapter now supports preauthorize, capture and void transactions for credit cards.
• Worldpay (WOR-EP1-CC): The API documentation has been updated to include information on which parameters are mandatory for the Worldpay WPG PCI adapter.

Fixed​

• ATOM (an NTT DATA Company) (ATOM-EP1-CC): Fixed an error with retrieving the settlement that was introduced in an earlier change.
• Braintree (BRA): The createdAt timestamp supplied in Braintree's postback is now used as the timestamp for PayPal chargebacks.
• DPO Pay (PAYGA): Fixed an issue that prevented settlements from being processed due to an invalid date format.
• EPG Financial Services Limited (EPG-EP01-PAYLA): If the additionalId1 field is not provided as part of the payout request, the alias of the referenced debit transaction is used as a fallback option.
• GoCardless (GOC-EP1): Fixed an issue with the server-to-server flow caused by a missing parameter.
• Valitor (VALIT-EP1-CC): Fixed an issue with settlements caused by duplicate transaction lifecycle IDs.

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​

Added​

• Transaction API: Updated the API response to include the schemeReferenceIdentifier field.

Features​

Changed​

• Performance Optimization: Improved performance of the admin UI for users with many locked transactions.
• Post Processing Jobs: Added a new post-processing option that calculates the sum total for line items with the same type and details (e.g. chargebacks) in the data export. A new field, thisLineItemValue sum has been added for this purpose.

Added​

• Push Adapters: The OfflineInvoice and SepaDummy adapters now support preauthorize, register, capture, void, refund, debit and payout transactions, allowing these transactions to be included in IXOPAY.

Fixed​

• Currency Conversion: The New Deviation Tolerance button is now only displayed if the user has permission to edit deviation tolerances.
• Currency Conversion: Fixed an issue where a JSON response was received instead of an HTML page when pressing Enter while entering data for deviation tolerances.
• Customer Profiles: Fixed an issue that caused a new customer profile to be added when sending a paymentToken of an existing customer profile by supplying a transactionToken and a customerProfileData.customerIdentification in the request.
• Customer Profiles: Fixed an issue with how deleted customer profiles are handled.
• Provider Setting: Only a single rolling reserve configuration can now be defined per payment method.
• Provider Settlements and Reconciliation: The timestamp for when a transaction was last modified is now updated correctly in the settlement status.
• User Settings: Fixed permissions for merchants assigned to sub-tenants.

Adapters​

Changed​

• dLocal (DLO-EP1): Extended the dLocal adapter to support transactions in Ecuador.
• dLocal (DLO-EP1-BT): Added support for bank transfers in Costa Rica.
• Straight2Bank Pay (STRAI-E01): Added a new option checkPaymentMethod for Straight2Bank settlements that only retrieves Billdesk transactions with the status CREDITED but not with the status SUCCESS.
• Valitor (VALIT-EP1-CC): The ValitorPay adapter now supports network tokens.

Added​

• Braintree (BRA-EP1): Extended the Braintree adapter to support Venmo as a payment method.
• Braintree (BRA): Switched from a deprecated SDK version to the latest version, migrated from checkout.js to JS SDK and added support to passthrough items, shipping/billing address details, invoice ID, discounts and shipping costs.

Fixed​

• ATOM (an NTT DATA Company) (ATOM-EP1-CC): Fixed an issue that caused the signature to be calculated incorrectly if data contained special characters.
• Braintree (BRA-EP2): Updated the handling of Braintree disbursement and settlement handling to reflect the file structure supplied by Braintree for Interchange plus (IC+).
• EquensWorldline (EQW-EP2): Fixed the handling of responses using v3 of the API.
• Mashreq (MASH-EP01-CCRD): Fixed the mapping of transaction IDs in settlements for Mashreq.
• Nets Group (NETS-EP1): Fixed an issue with the Nets widget not displaying correctly on payment pages.
• Nuvei (NUV-EP1-CC, NUV-EP2-CC): Fixed an issue caused by Nuvei no longer providing the auth code in callbacks, which would cause refunds to fail.
• Nuvei (NUV-EP2): Fixed the mapping of errors to IXOPAY error codes.
• PAYONE (PASIX-EP1-CC): Added a new payment reference for Six that is valid for all countries.
• Volt (VOL-EP1): Fixed the mapping of Volt transactions in settlements.

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.