Skip to main content

3 posts tagged with "Provisioning API"

View All Tags

v.24.8

API​

Fixed​

  • Provisioning API: The frontend.dashboard.show permission, used to grant access to dashboards, has been added to the Provisioning API.

Features​

Added​

  • Blocklist: Extended the blocklist to include the ability to define automatic blocklist rules. These can be used to add credit cards to the blocklist based on the merchant advice code ("Do not retry") or error code.

Fixed​

  • User Management: Fixed an issue with sending account recovery emails that would cause an error if the email failed to send.

Adapters​

Changed​

  • 2C2P (2C2P): Improved the error displayed when no transaction method is defined to better indicate the cause of the error.
  • 2C2P (2C2P-EP1): Refunds in 2C2P settlements are now handled.
  • PayPal (PPA-EP1-PPE): Added support for the Pay Later method to the Braintree adapter.
  • Sampath Bank (SAMPA-SVNP1): Added support for credit card payments via redirect.
  • Valitor (VALIT): Updated the adapter to automatically create a second chargeback if included in the settlements received from Valitor.
  • Worldline (ING-EP2): Improved the mapping of error codes based on the specific error, rather than just the HTTP status code.
  • Worldpay (WOR): Chargeback reversals for credit cards are now handled in settlements and included as line items.

Fixed​

  • Adyen (ADY-EP3): Fixed an issue that could result in long request processing times caused by transactions being locked when multiple postbacks are received simultaneously.
  • Nexi Group (NETS-EP2): Fixed the incorrect mapping of adapter error messages.

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

API​

Added​

  • Provisioning API: Two new fields have been added to the merchant response model: ntsEnrollmentStatus and networkTokenizationEnabled.

Features​

Changed​

  • Job Configuration: Information on inherited job type templates is now displayed, informing users as to why the template cannot be edited.

Added​

  • Network Tokenization:
    • Information on the status of enrollment for network tokenization is now available in the base data for a merchant. A new line, "Network Tokenization" has been added. If the merchant has a TRID assigned, the status is displayed as "enabled" when viewing the data as an admin with the permission "tokenization.networkTokenization.enrollment.show".
    • Merchants can now be filtered by their NTS status in the overview.

Fixed​

  • Pay-by-Link: Fixed an issue with the virtual terminal's result page not updating correctly if the initial transaction fails. Instead of displaying transaction data from the most recent (successful) transaction, data from the first (failed) transaction continued to be displayed.
  • Provider Settlements: Fixed an issue that would cause chargeback reversals to be created for the debit transaction, instead of the chargeback transaction.
  • Transaction List: Fixed an issue that would cause an error in the advanced search when changing the comparison operator from a range to any other operator.
  • Transaction List: Fixed an issue with sorting credit card fields. Note that BIN data cannot be sorted.
  • User Management: The frontend.statistics.show permissions now governs access to the pivot table as well.
  • Virtual Terminal: Fixed an unhandled exception in the virtual terminal that would occur if the fee set or fee entity was not found. The exception is now handled and an empty surcharge value is returned.

Adapters​

Changed​

  • Adyen (ADY): The payment reference for settlements is now saved.
  • Amazon Payment Services (AMAZO): It is now possible to filter transactions by the status "Accepted".
  • MultiSafepay (MUL): Added the chargeback reason for chargebacks.
  • Stripe (STRV2-EP1-MAS): Additional data from the Stripe API response is now included in the postback's extraData.

Added​

  • dLocal (DLO-EP1): Added support for the Sinpe payment method. This method supports bank transfers in Costa Rica.
  • Worldline (ING-EP2): Added support for payments via Trustly.
  • Zona Virtual SA - Zonapagos (ZONA-EP1-ZP): Added a generic payment method that redirects to the Zona Pagos payment page. The consumer can then select the desired payment method on this page to initiate the transaction.

Fixed​

  • Adyen (ADY-EP3-BIZ): Fixed an issue that would cause transactions that had been processed successfully to be assigned the status error or pending.
  • checkout.com (CHE): Fixed an issue that would cause an error when retrieving the session ID.
  • eMerchantPay (EME-EP3-SEP): Fixed an error that would occur if the customer was not an IBAN customer.
  • Mashreq (MASH): Fixed an issue when checking 3DS credentials that would cause a type error.
  • Mercado Pago (MERPA-PROD): Fixed an issue with register transactions caused by the Amount For Card Verification not being included in the request to retrieve the issuer and payment method ID from the PSP.
  • Skrill (SKR-EP1): Fixed an issue related to email addresses not being tied to a Skrill account when requesting a payout. This would cause the payout to fail.
  • Volt (VOL): Fixed an issue caused by incorrectly handling errors in a response as a result.

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

API​

Fixed​

  • Provisioning API: Fixed an issue with the Provisioning API that would prevent the creation of vault connectors under specific circumstances.

Features​

Changed​

  • Fee Engine: Changed the behavior for configuring GST fees to reflect the Surcharge dependencies.

Added​

  • 3DS: The highest-supported 3DS version is now used where possible (i.e. 3DS v2.2.0 is used instead of v2.1.0). For more details, see 3DS 2.1.0 EOL and Changes to 3DS in IXOPAY.
  • Connector Settings: A new connector setting has been added (Postback/Status: Include isAFT in postback/status response) that includes information on whether AFT was performed using this transaction.
  • Post Processing: Added the ability to check whether data fetchers are set up correctly after adding or editing the data fetcher (currently only supported with the SepaExpress v1 settlement data fetcher). Results are shown in the data fetcher edit view.
  • Risk Profile: Added a filter check for all transactions with a payment instrument where the doNotResubmit flag is set for the Count of transactions using same payment instrument risk rule. Added the transaction's error status (error_adapter, error_internal, cancelled, invalid) to the transaction's status selection for the Count of transactions using same payment instrument risk rule.
  • Translation: Added Croatian and Slovenian to the merchant admin interface.

Fixed​

  • 3DS: When external 3DS solutions are used, the values are no longer included in the postback, as IXOPAY can neither guarantee they are correct nor complete.
  • Customer profiles: Fixed an issue that resulted in an incorrect wallet reference ID being entered in customer profiles.
  • Multi-method connector: Fixed an issue relating to the retrieval of customer profiles when used in combination with multi-method connector.
  • Search: Fixed an issue that prevented the advanced search filters from working with certain adapters.
  • Transaction List: The URL included in the transaction tree on the transactions details page not link to the transactions view.
  • Transactions: Fixed an issue where sending an amount without specifying a currency would set the amount to 0 for void transactions. This resulted in a full void instead of a partial void.
  • UI: Fixed the tooltips in the screens used to edit connectors.
  • UI: Fixed the responsive styling for the 3DS configuration, making values easier to see.

Adapters​

Changed​

  • 2C2P (2C2P, 2C2P-EP1-CC): Added the option to ignore scheme fees to the settlement data fetcher configuration.
  • Braintree (BRA-EP2-CC): Added support for a new disbursement file.
  • Braintree (BRA-EP2-CC): The Braintree adapter now supports the new settlement file format for Myanmar.
  • Checkout.com (CHE-EP1): Added the ability to configure a private key for the Checkout.com settlement data fetcher.
  • DPO Pay (PAYGA-PYGT-CC): Added a new Private key parameter that can be configured at the connector level for SFTP servers.
  • EquensWorldline (EQW-EP2): Changed from v2 of the API to the new v3 API.
  • Mastercard Payment Gateway Services (MPG-EP1-CC): Added support for Westpac settlement file handling.
  • Trustly (TRU-EP1): The response status can now be configured and failed payouts are set to FAILED.

Added​

  • Straight2Bank (STRAI-E01-MPESA): The Straight2Bank adapter now supports M-Pesa as a payment method.

Fixed​

  • American Express (AMX-EP1-AMX): Fixed the handling of chargebacks and chargeback reversals in settlements for American Express.
  • Bank of America (BOFA-EP1-ACH): Fixed an issue that caused export errors due to missing mandatory data.
  • Bank of America (BOFA-EP1-ACH): Fixed an error regarding the export of routing number extra data in the NACHA export for Bank of America.
  • DOKU (DOKU, DOKU-EP01): Added support for refund transactions ini DOKU settlements.
  • DOKU (DOKU, DOKU-EP01): Fixed the mapping of settlement fees and the handling of settlement amounts for the DOKU adapter.
  • DPO Pay (PAYGA-PYGT): The DPO settlement parser has been updated to handle the new CSV structure of the settlement files.
  • DPO Pay (PAYGA-PYG): Fixed the SFTP login to include the mandatory private key.
  • Mashreq (MASH-EP01-CCRD): The default currency for the Mashreq adapter has been changed to QAR.
  • PAYONE (PASIX-EP1-CC): Updated the configration for Six settlements to allow a customer-specific key to be entered.
  • Redsys (RED-EP2-BIZ): Added support for HMAC_SHA256_V1 as a signature version for merchant integrations.
  • Straight2Bank (STRAI-E01): Fixed the handling of refund settlements for Straight2Bank.
  • Trustly (TRU-EP1): Fixed the handling of Trustly credit notification events for payouts to update the status to error and prevent chargebacks from being created.
  • Volt (VOL-EP1): The bearer token status was re-added to the status request header after it was inadvertently removed.
  • Volt (VOL-EP1): Updated the handling of Volt settlement files.
  • Worldline (ING-EP2): Fixed a bug regarding the handling of webhooks.
  • Worldpay (WOR-EP1): Fixed an issue that caused the settlement data fetcher to retrieve multiple settlements if the same settlement file was uploaded more than once.

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.