Skip to main content

12 posts tagged with "eMerchantPay"

View All Tags

Gateway β€” v26.18

Gateway API​

Changed​

  • Customer profiles API: Add the option to either detach or to detach and deregister payment instruments.
  • PCI API: Add surchargeAmount, gstAmount, and totalAmount to the transaction response whenever a surcharge is present.

Gateway Features​

Changed​

  • Customer Profiles: Extend the use of stored payment instruments to multi-method connectors and wallet connectors.
  • Pay-by-Link: Add the ability to include values determined after payment processing (e.g. external risk check) in the result page.

Fixed​

  • Network Tokenization: Fix an issue where wallet transactions were submitted for network tokenization.
  • Network Tokenization: Fix an edge case where the system attempts to use a non-existent network token.
  • Pay-by-Link: Fix an issue when cancelling an ongoing transaction.
  • Transaction Details: Fix duplicate BIN lookup entries being added to the transaction log.
  • Transaction Processing: Fix an issue where Apple Pay and Google Pay transactions could fail with an incorrect token error in certain scenarios.

Gateway Adapters​

Changed​

  • Dimoco (DIM): Match fraud records (SAF + TC4) to transactions and flag them as fraud.
  • Euronet (EUR): Add support for payouts.
  • JPMorgan Chase (CHA): Update documentation for ACH Direct Debit.
  • PayPal Complete Payments - PPCP (PPCP): Add support for multiple billing agreements between the merchant and the customer which can be configured either via connector config or extra data.
  • Worldline (ING-EP5-CC): Add support for network tokens.

Added​

  • MerchantE Solutions (MES): MerchantE Solutions is a US-based payment processor and gateway, enabling secure Credit Card payments for e-commerce merchants. The new adapter supports Debit, Preauthorize, Capture, Void, and Refund transaction types.
  • Reflect (REF): New push adapter Reflect, a digital mobile banking app in Jordan powered by Arab Bank that offers seamless money management, digital transfers, and daily financial services.
  • Upay (UPAY): New push adapter Upay, a mobile financial service in Bangladesh offering fast, secure money transfers, bill payments, and mobile recharges.
  • USIO (USIO): USIO is a US-based payment processor offering integrated credit card and ACH payment solutions. The new adapter supports the payment method ACH for transaction types Debit, Register, Void, Refund, and Payout. ACH (Automated Clearing House) is an electronic funds-transfer network in the United States, enabling bank-to-bank payments.

Fixed​

  • Dimoco (DIM):
    • Fix the foreign exchange gain/loss handling in the reconciliation process.
    • Fix an issue where reconciliation records are occasionally being matched to the wrong transaction due to shortened reference ids.
  • eMerchantPay (EME-EP3): Fix an issue where customer data was missing on recurring transactions.
  • JPMorgan Chase (CHA-EP3-ACH):
    • Fix an issue with the hosted payment page flow.
    • Fix a bug where the transaction status is prematurely set to success.

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.

Gateway β€” v26.8

Gateway Features​

Added​

  • User Management: Add read-only access to Global Routing Profiles and Connector Aliases, allowing users to view configurations without the ability to make changes.

Fixed​

  • Dashboard: Fix an issue where the date range filter calendar in the dashboard was not responding.
  • Network Tokens: Fix an issue where customer profiles did not process with network tokens.
  • Provider Settlements and Reconciliation: Fix an issue where amounts in settlement export reports for CAMT.053 files could be negative.
  • Transaction Processing: Fix payout responses to include merchant advice codes in the transaction result.

Gateway Adapters​

Changed​

  • checkout.com (CHE-EP1-CC,CHE-EP2-CC):
    • Add documentation for the extraData.digitalGoods:type parameter for Account Funding Transfer transactions.
    • Add support for partial authorization, including the authorized amount and status, in transaction responses and callback notifications.
    • Add the network decline code and merchant advice codes to transaction responses and callback notifications.
  • Dimoco (DIM): Adjustments to commission and scheme fee handling.
  • dLocal (DLO-EP1-PUNTO): Add support for payments in Nicaragua via the PuntoXpress payment method.
  • eMerchantPay (EME-EP2-SEP): Include the mandate reference in the callback notification for recurring direct debit transactions.
  • JPMorganChase (CHA): Add a new dedicated line item to aggregate fees for disputes.

Fixed​

  • Dimoco (DIM): Fix an issue where settlement files are incorrectly imported multiple times.
  • Nuvei (NUV-EP1-CC): Fix an issue when using customer profile tokens for subsequent transactions.
  • PayPal Complete Payments - PPCP (PPCP-EP1-CC): Fix an issue where the payment instrument was not properly registered through the hosted payment page using customer profiles.
  • PayU (PAU): Fix an issue where settlement files containing dates in an alternative format were not parsed correctly.

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.

Gateway β€” v26.5

Gateway Features​

Changed​

  • Connector Settings: Add bracket notation for the connector setting Field Expression Operation for the target field extraData to allow dashes in the key name.
  • Network Tokenization: Add an additional network token configuration to the existing setting to allow creating network tokens when processing subsequent transactions.

Fixed​

  • Network Tokenization: Fix an issue where disabling network token processing also disabled network token creation.
  • Transaction Details: Fix a bug where transaction logs are not properly formatted.
  • Transaction Processing: Fix automatic capture to also work for failover transactions.
  • UI: Fix the customer profile list view showing a wrong total number.
  • Virtual Terminal: Add missing translation in the Pay-By-Link UI.

Gateway Adapters​

Changed​

  • Adyen (ADY): Add handling of Merchant Advice Code from callback notifications.
  • Braintree (BRA-EP1-SWI): Add support for Swish, a Swedish mobile payment method that allows customers to make real-time payments using their phone number and banking app.
  • checkout.com (CHE-EP2-BIZ): Add the payment ID in the callback notification as psp:bizumPaymentId.
  • dLocal (DLO-EP1): Add a new optional configuration setting which allows sending a custom X-Dlocal-Payment-Source header.
  • eMerchantPay (EME-EP3-CC): Add support to automatically migrate existing recurring card subscriptions from the legacy platform to the Genesis platform without requiring cardholders to re-register.

Added​

  • NaverPay (NAV-EP1): NaverPay is a South Korean digital wallet and online payment platform by Naver Corporation. It enables users to make seamless payments across e-commerce sites, apps, and offline merchants. The platform offers secure transactions, loyalty rewards, and easy integration for businesses.

Fixed​

  • KCP PC (KCPPC): Add a temporary configuration setting which should fix issues with refunds.
  • PayPal Complete Payments - PPCP (PPCP-EP1-PPE): Fix an issue with the wallet reference handling.
  • Redsys (RED-EP2-BIAPI): Fix an issue where the authCode is not included in the callback notification.

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.

Gateway β€” v24.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.

Gateway β€” v24.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 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.