Skip to main content

15 posts tagged with "Braintree"

View All Tags

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

v.24.11

Features​

Changed​

  • Account Updater: The information on when a customer's card was last updated only displays the date, not date and time. The documentation has been updated accordingly.

  • Meta connector (Multi-method connector): A number of changes have been implemented:

    Routing rules view:

    • Disabled and archived connectors are now only displayed if they are used in the routing rule. If such adapters are used, the adapter is displayed with the "(DISABLED)" prefix.
    • If a connector used in a routing rule is disabled or archived, the rule can no longer be saved. A suitable error message is displayed.

    Connector configuration:

    • When a connector is disabled or archived, the system first checks whether the connector is used in any routing rules. If the connector is in use, a warning is displayed that connectors can only be disabled or archived if they are not used by any routing rules. A list of the routing profiles using the connector is also displayed.

    Meta-connector configuration:

    • When unarchiving a meta-connector, its status is automatically set to disabled.
    • When enabling a meta-connector, the system checks whether the meta-connector uses any disabled or archived connectors. A corresponding message is displayed if the meta-connector cannot be enabled due to it referencing disabled/archived connectors.

Fixed​

  • Virtual Terminal: The merchant transaction ID is now a mandatory field in the virtual terminal.

Adapters​

Changed​

  • ATOM (an NTT DATA Company) (ATOM-EP1-CC): Added post-processing logs.
  • Braintree (BRA-EP2-CC): Added support for chargeback and chargeback reversals for disbursement and fee settlements.
  • Redsys (RED):
    • Updated the documentation to include information on the new configuration and parameter mapping.
    • Added a merchant descriptor configuration to DS_MERCHANT_MERCHANTDESCRIPTOR
    • Mapped the description to DS_MERCHANT_MERCHANTDESCRIPTOR.
  • Silverflow, Stripe (SIL-SEP-VIS, STRV2-EP1-VIS): Updated the documentation with information that final captures are supported by the adapter.
  • Worldline (ING-EP1-CC): Increased the timeout to 60 seconds when retrieving settlement files.

Added​

  • CMI (CMI): The payment acquirer CMI has been a trusted partner of Moroccan merchants since 2004. The CMI adapter supports payment via credit card.

Fixed​

  • eMerchantPay (EME-EP3-SEP): Fixed a bug which caused partial refunds to be declined by the gateway, even though this transaction type is supported.
  • HypYaad (HYP-EP1-CC): Fixed a bug that caused transactions with an amount higher than 999.99 to be ignored in settlements.
  • PayPal (PPA, SHO): Fixed an issue that would occur when configuring a data fetcher for either PayPal or Shopify PayPal without the necessary required parameters. The user name and password in the configuration are now also shown as required.
  • Worldline (ING-EP5): Updated the way transactions are voided to include additional information on the payment amount and currency. The status handling was also reworked to improve error handling and the accuracy of 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.

v.24.9

API​

Added​

  • Transaction API: Added cardUpdateStatus and cardUpdatedAt to returnData for cardData responses when account updater is enabled.

Features​

Added​

  • Account Updater: The Payment Instruments section of Customer Profiles now shows the Status and Last Update columns for Credit Cards.
  • Meta connector: Added support for tokenizing Google Pay and Apple Pay payment information and routing these transactions to PSPs.

Fixed​

  • Post Processing Jobs: Fixed an issue with the option to pause the execution of post-processing jobs. Previously, setting the job to wait until a specific time that included seconds meant that the next strategy job was never executed.
  • Provider Settlements and Reconciliation: Settlement conflicts are now resolved as a result of the transaction being set to successful.

Adapters​

Changed​

  • Adyen (ADY-EP3-CC): Added support for post-processing Adyen settlements and reconciliation via GlobalPayments.

  • Braintree (BRA-EP1-BLI): Added support for the Blik payment method. This is a popular bank transfer payment method in Poland.

  • Redsys (RED-EP1): Added a new setting for the Redsys Bizum payment method that allows users to include an error URL in the transaction data. If the URL is specified, the system will send this URL if the payment fails, improving error handling and the user experience.

  • Worldline (ING-EP5): PostFinancePay is now available as a payment method. The following countries are supported:

    • Switzerland
    • Belgium
    • France
    • Germany
    • Netherlands
    • United Kingdom
    • Additional EU countries

    Supported currencies include CHF and EUR.

Added​

  • AllSecure (ALLSE): AllSecure is a global payment service provider that provides tailor-made online payment solutions. The adapter supports credit card payments.
  • PayPal Complete Platform (PPCP-EP1-PPE): Added a new PayPal Commerce Platform adapter. The adapter supports:
    • All transactions types using hosted payment pages
    • All transaction types by integrating PayPal directly on the merchant's website
    • PayLater capability
    • PayPal vaulting.

Fixed​

  • Adyen (ADY): Fixed an issue where lines marked as a merchant payout were not correctly mapped to the paymentReference field.
  • checkout.com (CHE-EP1-IDE, CHE-EP2-IDE): Added BIC support for transactions not involving an IBAN customer.
  • Neteller (NET-EP1): Fixed an issue where the transaction status failed to update to ERROR after receiving a postback indicating an error.
  • Worldline (ING-EP2-MAS): Fixed an issue with unformatted chargeback amounts. Due to the lack of formatting, the result was increased by a factor of 100.

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.

v.24.6

Features​

Changed​

  • Post Processing Jobs:
    • The Collect Transactions by Uploaded CSV File post-processing job now allows multiple fields (arn, uuid, and adapterTxid) to be mapped. Previously, only the arn field could be mapped.
    • A new setting has been introduced, Cascading ID Mapping. If this option is activated, IXOPAY attempts to locate related transactions for every mapped identifier (in the same order as the fields are mapped in the post-processing job). If a transaction is found, it is added to the post-processing job, while all other identifiers in the CSV are ignored for that transaction.
  • Provider Settlements and Reconciliation: Improved the error message that is displayed when a transaction cannot be found due to a missing reference in the settlement file.
  • UI Navigation: New permissions have been added that determine whether users can access the dashboard (dashboard.show and frontend.dashboard.show). Existing users and roles will automatically receive these permissions. A welcome page is now displayed as the start page for users without access to the dashboard.

Fixed​

  • Fee Management: Fixed an issue that meant it was possible to save fees even when the mandatory feeStrategyParameters field did not contain a value.
  • Fee Management: Fixed an issue where the amount was incorrect in retried transactions, as the amount would include previous surcharges if the surcharge was calculated dynamically.
  • Post Processing Jobs: Fixed an issue that prevented more than 1,000 connectors from being assigned to a post-processing job schedule.
  • Provider Settlements and Reconciliation: Fixed an issue that caused the delete button to be displayed for canceled transactions. The button is now only displayed if the status of the settlement is "new".
  • Provider Settlements and Reconciliation: Fixed an issue with resolving transactions by additionalId.
  • Transaction List: Fixed an issue with sorting by card type in the Transaction List.
  • Transaction List: Fixed an issue in the Transaction List filters that would cause no results to be returned if a filter was applied to the first 8 digits of the card number.
  • UI Navigation: Fixed an issue where the red highlighting of missing reconciliations was not applied when switching pages or applying a filter.
  • Virtual Terminal: Fixed an issue with surcharge fee calculations.

Adapters​

Changed​

  • GoCardless (GOC-EP1): GoCardless settlements now also include payment references.

Fixed​

  • Adyen (ADY): Fixed an issue caused by the Izyco settlement data fetcher configuration parameter missing the regular expression for the file name.
  • Braintree (BRA-EP1): Improved the handling of the billing address. If the extra data fields for company, first name or last name are unavailable, the company, first name and last name are taken from the Customer object.
  • checkout.com (CHE-EP1-CC, CHE-EP2-CC):
    • Fixed an issue that would cause the status of a transaction to be set to ERROR if a callback is received that is not mapped in IXOPAY.
    • The following callbacks are now handled:
      • authorization_declined
      • card_verification_declined
      • card_verified
      • authentication_started
      • authentication_approved.
    • Added the mandatory provessingChannelId parameter for the NAS platform.
  • Nexi Group (NETS): Fixed an issue with settlements caused by a missing configuration.
  • PayU (PAU-E01): Fixed an issue that would cause a backend error if the payment_id is missing in the payload during callback processing.
  • Stripe (STRV2): Fixed an issue with Stripe settlements where transactions in IXOPAY were not correctly identified.
  • Volt (VOL): Fixed an issue with retrieving 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.

v.24.4

API​

Added​

  • Transaction API: The "account closed" error for PCI adapters has now been mapped to error code 2001 in IXOPAY and treated as a hard decline.

Features​

Changed​

  • Alerts: Instead of sending out separate emails for each alert, email notifications are now sent out periodically. These emails will collect all alerts received over a time period in a single email. The default time period is 5 minutes, but can be configured individually for each notification category.

Added​

  • Provider Settlements and Reconciliation: Added a new feature to allow dummy settlement files to be created in order to test various post-processing features. The "Test Settlement" option is accessible from the "Provider Settlement" page. This page has been reworked and the UI has changes as a result. A new permission, postprocessing.provider-settlement.create, has been added. This permission must be enabled in order to access the "Create Settlement", "Upload Settlement File" and "Test Settlement" actions. The old permission, postprocessing.provider-settlement.settlement-upload, has been removed. If this permission was previously active, the new permission will be active by default.

Fixed​

  • Job Configuration: Fixed an issue where two Save buttons were displayed when editing job configurations.
  • Transaction List: Ignore tenant name in the transaction list if only the "Include Sub-Tenants" checkbox was checked.
  • UI Navigation: Fixed an issue where styling was not applied to conflicted transactions after applying a filter.
  • UI Navigation: Fixed issues with sorting the transaction list by cardholder, first 6-8 digits, last four digits and card type. The table can no longer be sorted by card level, card bank and card country.

Adapters​

Changed​

  • Neteller (NET-EP1-NET): Added support for payouts.
  • Paynetics (PNE-EP1-CC): A new data fetcher setting, "Split settlements by PayCurrency", is now available. If enabled, settlements are split by currency and the PayCurrency is used as the SettlementCurrency.
  • Skrill (SKR-EP1-SKR): Added support for payouts.

Added​

  • JCC Payment Systems (JCC): JCC Payment Systems leads Cyprus' payment-processing sector, supporting merchants and financial institutions for nearly 30 years.

Fixed​

  • Adyen (ADY-EP3): Disabled refunds for the Multibanco payment method, as refunds are not supported for this payment method.
  • Braintree (BRA-EP1):
    • Fixed an issue that would result in an error if the customer was empty in a transaction.
    • Fixed an issue that occurred if the public or private key were null values.
  • China UMS (UMS-EP1):
    • Fixed an issue where white space was included in requests when no customer name is provided.
    • Fixed the mapping of callback data in the extraData field.
    • Fixed an issue with integer values in the extraData. Integer values are now converted to strings.
  • Klarna (KLW-EP1): When creating a session, the merchant_reference2 field is now also included. This provides additional information for identifying the transaction.
  • Straight2Bank Pay (STRAI-E01): Fixed an issue that would occur if the encryption key and payload were missing. The system now checks whether these values are present, and a correspoing error is returned if this is the case.

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.