7 posts tagged with "Transaction API"

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

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: Settlements can now be resolved using all available IDs.
• Provider Settlements: 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.

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.

API​

Fixed​

• Batch API: Addressed issues with the conversion of files from CSV to JSON, and conflicting UUIDs due to latency between the time when a transaction is submitted and actually processed.
• Transaction API: Fixed an issue where if a failover transaction returns a merchant advice code, this MAC is not returned by the origin transaction. The MAC is now returned by the origin transaction.

Features​

Changed​

• Customer Profile: It is now possible to use the UUID or payment token from a customer profile to request a CVV refresh via payment.js. This makes it possible to ask the customer to enter their CVV for transactions using a stored credit card.
• Post Processing Setting: Postback notifications are now sent when creating an "unknown" transaction.
• UI: Information on the possible impact of daylight savings time is now displayed when editing job schedules.
• User Management: Any changes to merchant users now require additional confirmation, and a message is displayed that these changes may have an effect on live processing.

Fixed​

• Global Connector Settings: Transaction expiry settings are now displayed in the connector's global settings section.
• Post Processing Job Configuration: The calculation of the net settlement amount in the "Write customized Settlement CSV" job step is now the same for refunds and chargebacks.
• Risk Profile: The "Allowlist" and "Blocklist" risk rules no longer list credit card-related options such as the BIN and CC fingerprint for the meta-connector, as the card cannot be evaluated at this stage of processing.

Adapters​

Changed​

• Bitpay (BTP-EP1-CR): BitPay pairing has been moved to the connector's Additional Configuration tab.
• dLocal (DLO-EP1): Support has been added for PuntoXpress and PayCash in Costa Rica.
• HUA NAN COMMERCIAL BANK (HNCB-EP2-HBQR): The key version used for encryption is now a configuration option.
• Paynetics (PNE-EP1-CC): Added API documentation for Paynetics.
• PAYONE (PASIX-EP3-CC): Added API documentation for Payone.
• Worldline (ING-EP2-CC): Fixed an issue where tokens are flagged as single use when they should be flagged as recurring. These tokens can now be reused.

Added​

• Adyen (ADY): Added a new data fetcher for settlements provided by Izyico.
• Zona Virtual SA - Zonapagos (ZONA): Zona Virtual is a Colombian company with 23 years of experience in the e-commerce sector. The ZonaPagos adapter support payments via credit card and Pagos Seguros en Línea.

Fixed​

• checkout.com (CHE): Added support for "Partial Capture" settlement entries.
• GoCardless (GOC): Fixed an issue with register transactions in the new server-to-server flow.
• Nuvei (NUV-EP1-CC): Updated the API documentation to include mapping information.
• Shift4 (CRE-EP1-CC): Fixed an issue with how UUIDs are formatted in failover transactions.
• Sofort (SOF-EP2-SOF): Fixed an issue with refunds that would change the status of the original transaction from success to error.
• Unzer (UNZER-EP1): The orderId in capture requests now uses the additionalId1 in the preauthorize transaction.
• Valitor (VALIT-EP1-CC): Fixed an issue with duplicated preauthorize transactions in settlements.

Misc​

Added​

• API Documentation: Updated the API documentation to include information on the bin_digits parameter.

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: Added dedicated fields for the cardholder billing state (billingAddressState) and cardholder shipping state (shippingAddressState) used in 3DS authentication.

Features​

Changed​

• Permissions: Front end user roles have been split into view and edit permissions.
• UI: Autocompletion of password input fields has been disabled as a security measure.

Fixed​

• Multi-method Connector: Fixed an issue with converting register transactions to debit/preauthorize transactions for adapters that do not support register transactions directly. This conversion would fail when using multi-method meta-connectors in conjunction with the processing:convert-register-to-debit setting.
• Post-processing Schedule: Fixed an issue in calculating the post processing schedule interval.
• UI: Fixed the Token icon colour for white label tenants.

Adapters​

Changed​

• Klarna (KLW-EP1-APM): In order to support an upcoming change, the IXOPAY UUID is now provided via the merchant_reference1 and merchant_reference2 fields. IXOPAY now checks for the UUID in merchant_reference2 when handling settlements, using this value as a fallback until changes to the handling of the UUID are complete.
• Mashreq (MASH-EP01-CCRD): The response data is now used to set the transaction status instead of sending a separate request to retrieve the status.
• Valitor (VALIT-EP1-CC): Changed the Valitor ID used to map settlements, as the ID used previously could not handle certain cases such as refunds.

Added​

• Adyen (ADY-EP3-BIZ): Bizum has been added as a new payment method.
• AsiaPay (ASIA): AsiaPay is an Asian digital payment service provider, covering credit and debit cards, online banking, digital wallets, BNPL and other digital payments. The new adapter supports GCash, BPI and ShopeePay as well as credit card payments with JCB and Mastercard.

Fixed​

• eMerchantPay (EME-EP3): Fixed issues with invalid amounts that occurred when the currency is missing by using the related transaction's currency as a fallback.
• Worldline (ING-EP2-CC): Updated the adapter to use the same error mapping for adapter calls and incoming callbacks.

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.