12 posts tagged with "eMerchantPay" | Page 2 of 3

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​

Added​

• Job Configuration: To simplify the process of exporting settlement file data for enterprises with multiple merchants, the External ID stored in the provider can now be used to store an identifier for each merchant. This ID can be selected in export jobs, allowing the same export job to be used for each company/merchant in cases where there are otherwise no differences between the exports. Previously, an individual export needed to be configured per company/merchant.

Fixed​

• Account Updater: Fixed an issue with the Account Updater that would lead to an incorrect Status being displayed for batch updates ("Finished" instead of "Waiting").
• Account Updater: Fixed an issue with the new merchant overview where clicking on the details would not redirect users to the selected merchant, but to the selected tenant instead.
• Merchant Interface: Updated some translations and reviewed the Croatian and Slovenian translations.
• Pay-by-Link: Restricted the ability to cancel transactions to pay-by-link transactions only.
• Post Processing Setting: Fixed an issue that would prevent settlements from being retrieved if the waitForAllFiles setting is enabled. Incomplete periods are now also handled correctly, with the last period only being updated if settlement files were processed.
• UI: Fixed the 8-digit BIN display in the transaction details view.
• UI Navigation: Fixed the broken icon for creating connectors.
• Virtual Terminal: Removed trailing apostrophes for virtual terminal result URLs.

Adapters​

Changed​

• American Express (AMX-EP1): Reinstituted a change that was reverted in the last release. A reference number is generated and passed to the vault as part of the capture request using the additionalId1 field. However, this could not be handled using the multi-method connector.
• ATOM (an NTT DATA Company) (ATOM-EP1-CC): The data fetcher configuration has been updated, allowing additional field mappings for settlement files. The names of the fields selected here need to be added to the key column in the export job.
• checkout.com (CHE-EP2): Added payout parameters for platform 2.
• dLocal (DLO-EP1-PUNTO): The Punto Express payment method is now supported by the dLocal adapter.
• eMerchantPay (EME-EP3-SEP): Added support for deregister transactions.
• GoCardless (GOC-EP1): An additional configuration option has been added for the connector that provides a choice between redirect and server to server flows.
• Nuvei (NUV-EP2): Fixed the mapping of Nuvei error codes, with "Service Busy" now being mapped to IXOPAY error code 3003 (temporarily unavailable).
• Sepa Express (SEP-EP3-BTR): Added a new bank transfer payment method to the adapter. As this payment method uses open banking, some transaction types like register and deregister are unavailable, along with other transaction types not implemented in the original version of the adapter.
• SoftBank Payment Service (SOB-EP1): The documentation was updated to include information on required fields.
• Unzer (UNZER): Fixed the title for the Unzer API documentation.
• Valitor (VALIT-EP1-CC): Fixed an issue that would cause refunds to fail for capture transactions. Instead of requesting a refund, IXOPAY now requests a capture refund, which resolves this issue.

Added​

• AsiaPay (ASIA): AsiaPay is a leading payment service provider in the APAC region. The adapter supports GCash, ShopeePay and credit card payments.
• HypYaad (HYP-EP1-CC): Hyp is an Israeli all-in-one payments solution that provides online and in-store payment solutions. The adapter supports credit card payments.
• Unzer (UNZER-EP1): Unzer is a leading fintech company based in Germany, specializing in providing innovative and secure payment solutions. With a strong focus on e-commerce, Unzer offers a wide range of payment methods and services.

Fixed​

• American Express (AMX-EP1): Fixed an issue with fees in American Express settlements that would only occur under certain circumstances.
• AsiaPay (ASIA): The AsiaPay PesoPay logo is now displayed wherever the brand name is used instead of the adapter name.
• checkout.com (CHE-EP1): Fee reports are now handled in a second process, rather than as part of the settlement. A new data fetcher configuration (gross type) is available for this purpose.
• Klarna (KLW): Fixed an issue with validation that affected customers in specific locations. The validation now checks that the billingState is set if the country is US or Australia.
• Nuvei (NUV-EP1): Improved the parsing of the CSV settlement files to be more robust. Under some circumstances, an error could occur when parsing settlement files.
• Nuvei (NUV-EP1): Before parsing a row in the reconciliation file, the date is checked to ensure it is valid.
• Straight2Bank Pay (STRAI-E01): Fixed an issue that would cause the retrieval process for settlements to be locked if an invalid response was received.
• Unzer: Fixed errors caused when postback sharing is not set in the connector.
• Worldpay (WOR-EP1-CC): The adapter transaction ID is now set when an incoming postback 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​

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.

Features​

Changed​

• 3DS: Rolled back changes that removed 3DS postback data for merchants using external MPI.
• Transaction details: The payment token is now included in the customer profile data in callbacks and API status calls.

Added​

• Post Processing: The filter in the Collect All Transactions (in period) Post Processing collecting step now supports filtering adapter errors and internal errors by the date on which their status changed.
• Provider settlements and Reconciliation: Added a new tab to the conversion rate system settings that allows deviation tolerances to be defined for currency pairs per tenant. This is then used to verify settlements rather than the tenant's global tolerance or default tolerance (0.02%).
• Settings: Added a new project setting, Postback: Include Basic Auth header, which allows a header to be sent for basic-auth postback. This setting is also available as a global connector setting.

Fixed​

• Account Updater: Fixed an issue where only one level of sub-tenants were filtered. Fixed an issue that would cause an error when changing the master tenant in the detailed view.
• Customer profile: Fixed an issue that triggered an error when creating a customer profile via the API's customerProfileData field without setting any customer data in the transaction.
• Pay-by-Link: Fixed an issue that would result in an empty redirect URL. Fixed an issue with redirects to expired pay-by-link transactions without an error URL that would cause an exception. The correct page is now displayed.
• Pay-by-Link: Fixed an issue that caused all pay-by-link transactions to be withRegister transactions. It is now possible to choose whether the transaction should be a withRegister transaction or not using the with Register (Store Payment Instrument for Card-on-File payments) checkbox.
• Post Processing: Fixed an issue that would cause an error for sub-tenants when attempting to select job configuration templates created at the parent provider level if no fee entities were available in the template.
• Risk Engine: Fixed an issue with the Count of different credit cards of same device risk rule if no customer or browser data is available.

Adapters​

Changed​

• checkout.com (CHE-EP1-CC): The AVS and CVV results are now added to the extraData in callbacks if available in the response.
• DPO Pay (PAYGA-PYGT-PMR): Added support for the USSD payment method.
• eMerchantPay (EME): Added support for chargeback reasons, which are now forwarded to merchants.
• Nuvei (NUV): Updated the Westpac settlement handling.
• Paysafecard (PSC): Added support for payouts.
• Redsys (RED-EP2-BIZ): Added support for refund transactions.

Added​

• Nuvei (NUV-EP1-CC): Added support for chargeback notifications from Nuvei.

Removed​

• Bank of America (BOFA-EP1-ACH): The Addenda row was removed from the NACHA file when using the WEB format, as it is not required.

Fixed​

• Nuvei (NUV-EP1-CC): Fixed issues with the references to related transactions, which should either contain the Nuvei transaction ID, the transaction ID of the previous 3DS request, or the transaction ID of the authorized payment.
• Nuvei (NUV): To handle issues with settlements, a new optional configuration setting has been added for the reconciliation data fetcher ID, which checks whether the system needs to wait for the CB report for the same date when retrieving settlements.
• PPRO (PPR-EP1): Fixed an issue with settlements, that is caused by PPRO sometimes providing multiple files with the initial file only containing volume data, and subsequent files containing the actual transaction settlement data. A new option is now available in the data fetcher configuration, Only retrieve settlements if all fees and volume files are present that checks whether all settlement files are present before retrieving and processing the files.
• Valitor (VALIT-EP1-CC): Fixed an issue related to duplicate transaction IDs issued by Valitor that would cause refunds to be ignored in settlements due to another transaction having the same ID.
• Volt (VOL-EP1): Fixed an issue with Volt settlement files caused by the formatting of the CSV data.

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​

Added​

• Post Processing Jobs: Added a new configuration option in the job configuration Processing Step: Copy Line Items from related batch - Do not aggregate line items with the same name that allows two line items with the same name.
• Provider Settlements and Reconciliation: Added a new Provider Setting - Reconciliation: Create Provider Settlement with Conflict Log to handle settlements provided via reconciliation (e.g. PayPal) in cases where the transaction is missing or unknown.
• UI Navigation: The Customer Profiles and Account Updater have been moved to the Tokenization menu.

Adapters​

Changed​

• checkout.com (CHE-EP1): Aggregated payout information is now represented as line items in settlements. This includes interchange fees, scheme and network fees, provider fees, gateway fees and chargeback fees.
• DPO Pay (PAYGA-PYGT-PMR): Updated the parser to handle the updated structure in newer settlement files.
• eMerchantPay (EME-EP3): Removed the check that data has been entered in mandatory fields in EMPGenesis, as these mandatory fields can be disabled for the merchant by the PSP.

Added​

• Braintree (BRA-EP1-PPE): Added support for additional data (STC, AID, BN) required by Braintree for airlines and travel merchants when using PayPal as the payment method.
• Braintree (BRA-EP1-PPE): Added support for tenant-specific BN code which are included with pre-authorization and debit transactions.
• Braintree (BRA-EP2-CC): Added support for level 2/3 data for Visa and Mastercard transactions via Braintree.
• Mashreq (MASH-EP01-CCRD): Added a new adapter for Mashreq. Mashreq a leading financial institutions in the UAE that provides banking and financial services. The adapter supports credit card transactions and settlements.
• MultiSafepay (MUL-EP1): Added support for reconciliation and settlements for the Multisafepay adapter.
• PayPal (PPA-EP1-PPE): Wallet data (first name and last name) is now exposed under Additional Info for payouts and debits.
• Worldpay (ING-EP2): Added the option to configure an SFTP host and SFTP private key with optional SFTP passphrase instead of an SFTP password.

Fixed​

• BDO (BDO-EP1-GCASH): Risk check are now correctly applied to the BDO adapter.
• DPO Pay (PAYGA-PYGT-CC): Added a check for a mandatory description in refunds.
• PayPal (PPA-EP1-PPE): Fixed an issue handling the refund amount in partial refunds received via postback.
• PayU (PAU-E01-CC): Implemented a method for tokenizing cards using debit and refund transaction for Colombia, as authorization and register transactions are not supported.
• Redsys (RED-EP1-CC): Fixed an issue with the key length in the paramsKey extraData parameter.
• Volt (VOL-EP1): Fixed error handling during Volt settlement notification handling.
• Volt (VOL-EP1): By default the full list of banks is now retrieved for Volt. A subset of banks can be retrieved using parameters.page and parameters.limit.
• Worldline (ING-EP3-CC): Fixed Worldline Ogone TWINT settlement refund fee handling.

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.