Skip to main content

One post tagged with "Login"

View All Tags

Gateway — v.24.19

API

Changed

  • Status API: Exposes the acquirer reference number (ARN) via the field extraData["arn"] when it is available.
  • Transaction API: Exposes the acquirer reference number (ARN) via the field extraData["arn"] when it is available.

Fixed

  • Transaction API: Fix an issue where missing wallet data fields (walletOwner, walletReferenceId, walletOwnerFirstName, walletOwnerLastName, walletOwnerCountryCode) could cause an error. These fields are now treated as not provided.
  • Transaction API: Implement stricter currency format validation, requiring merchants to send amounts with the correct number of decimal places for each currency (e.g., EUR: 9.99 or 9.9, JPY: 5 or 5.00). If the correct format can't be provided by merchants, the tenant can be configured to round amounts commercially according to our currency definition. These settings are inherited by sub-tenants. For assistance in configuring this setting, please contact your customer success manager.

Features

Added

  • BI Data Source: Add a new data field, sub_type, for transaction subtypes related to rapid dispute resolution (RDR) in the BI data source.
  • Login: Store redirect data in the URL to ensure that after multi-tab logout and login, each tab returns to the originally requested page instead of the landing page.
  • Token Count Aggregation: Add filters to the post-processing step Calculate Token Count, allowing users to:
    1. Exclude Merchants having this Job Types scheduled
    2. Exclude Connectors having this Job Types scheduled
    3. Only Methods.

Fixed

  • Connector Configuration: Fix a bug in the transaction expiration process to ensure the Ignore Global Setting connector setting is respected whenExpire Pending Transactions or Expire Transactions is enabled.
  • Connector Configuration: Fix an issue where a valid value of 0 for the connector setting Postback Queue: Set maximum number of retries was incorrectly treated as missing or invalid. The system now properly accepts 0 as a valid input.
  • Documentation: Fixes the API authentication examples by removing the newline character that was incorrectly included in the base64-encoded concatenation of the username and password.

Adapters

Changed

  • 2C2P (2C2P-EP1-2C2PB): Update the payment channels by removing Thanachart Bank and adding the new TMBThanachart Bank following the merger with TMB Bank.
  • KCP Mobile, KCP PC (KCPMO, KCPPC): Add support for settlement handling.
  • Mercado Pago (MERPA-PROD): Adds a new header to the payment request containing the DeviceData. This allows the collection of the DeviceID when redirecting the user to the Hosted Payment Page (HPP).
  • PXP (PXP-EP1-CC): Map the field ProviderExternalID to acquirer reference number (ARN).
  • Stripe (STRV2-EP1-CC, STRV2-EP3-CC (extends STRV2-EP1-CC)): Add the ability to pass requestExtendedAuthorization as extra data to Stripe to request an authorization to be extended for up to 30 days.
  • Worldpay (WOR-EP1): Update AFT documentation.

Added

  • KakaoPay (KAKAO): Add the KakaoPay adapter with support for debit, refund and partial refund transactions. KakaoPpay is a South Korean fintech company specializing in digital payments, money transfers, and financial services.

Fixed

  • KCP Mobile (KCPMO-EP1):
    • Use Code as fallback response code if res_cd isn't available.
    • Fix an issue where the wrong value (payment method ID instead of payment method name) was sent for the pay_method field.
  • Nuvei (NUV-EP1-CC): Fixes the fail-over transaction to Nuvei by ensuring that the firstPaymentDoTransactionId is only set if the related transaction was created through Nuvei; otherwise, it is omitted to prevent rejected transactions.
  • PXP (PXP-EP1-INST): Fix wrong format of expiryMonth and expiryYear in adapter result.
  • Zona Virtual SA - Zonapagos (ZONA-EP1): Fix status retrieval handling to consider only the latest status, as recommended by the PSP.

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.