11 posts tagged with "Virtual Terminal"

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.

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.

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 and Reconciliation: 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.

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.

Features​

Changed​

• UI Navigation:
  • If the user only has access to a single connector, it is now automatically selected in the virtual terminal.
  • The last selected connector is stored locally to prevent having to re-select it for future transactions.

Added​

• BI Data Source: Scheme IDs are now available for post-processing.
• Connector Configuration: Added a new project setting, Manipulation: Field Operation that can be used to manipulate data at the connector level prior to sending the data to the PSP. It is currently possible to truncate the data after a defined number of characters using this option. More operations will be added in the future.
• Fee Management: Added the ability to specify the customer's billing state for fees.
• UI Navigation: Added information on the deployed version to both the gateway and documentation.

Fixed​

• Fee Management: Fixed an issue that would result in an error if no target fee set has been specified and the source fee set is assigned to a sub-tenant.
• UI Navigation: Fixed an issue that prevented archived jobs from being restored when in the table view.
• Virtual Terminal: Fixed an error that could occur when calculating surcharges if no credit card number has been entered.

Adapters​

Changed​

• American Express (AMX-EP1-AMX): Added support for Apple Pay.
• China UMS (UMS-EP1): Added the optional expireTime parameter to the payload. The value of this parameter is taken from the extraData field. If the parameter is not provided there, it is taken from the project settings.
• Cybersource (CYS-EP1-CC): The forwardedAcquirerCode field is now available for postback notifications.
• HypYaad (HYP-EP1-CC): Added support for settlements in CSV format and stored on an SFTP server.
• Klarna (KLW-EP1): The customer.birthDate field has been changed from required to optional.
• PXP (PXP-EP1-CC): The SchemeTransactionIdentifier, SchemeSettlementDate and DinersRetrievalReferenceNumber in callbacks are now stored for use in recurring transactions.
• SIA (SIA-E01): Added support for void and partial captures.

Added​

• Paymee (PAYME-EP1-CCRD): Paymee is a Tunisian payment gateway that accepts credit card payments via a redirect link.
• Sampath Bank (SAMPA-SVNP1-BTR): Sampath is a secure Sri Lankan online payment platform. The adapter supports bank transfers.

Fixed​

• Adyen (ADY):
  • When submitting a transaction using a hosted payment page, clicking on the back button caused the transaction to be resubmitted. This caused two transactions to be sent to the PSP, but IXOPAY only counts this as a single transaction. The duplicate transaction is automatically closed by the PSP, which can overwrite the correct transaction ID of the transaction in IXOPAY.
  • Fixed an issue with settlement notifications that caused settlements to be ignored.
• Amazon Payment Services (AMAZO):
  • A new option has been added that supports SHA-512 alongside the previously supported SHA-256 encryption. This setting should be configured in IXOPAY to match the one configured in the Amazon settings.
  • Fixed an issue generating settlement reports that would only occur when an existing settlement report was re-generated.
• China UMS (UMS): Fixed an issue that prevented the status of pending transactions from being polled correctly.
• China UMS (UMS-EP1): A refund order ID has been added, which now allows multiple refunds.
• Klarna (KLW-EP1): Fixed a number of issues that could occur in cases where the customer's birthdate is missing.
• NMI (NMI-EP1): Fixed an issue where a type error would occur if no related transaction is present and no extra data is set for a credit card connector. The expected data type is an array; if no data is available, an empty array is now used.
• Worldline (ING-EP6): Fixed an issue that could cause successful refunds to remain stuck in a pending state.

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.