2 posts tagged with "Login"

Gateway API​

Fixed​

• Provisioning API: Fix an issue where the callback notification format 3-512 (JSON, SHA512-enforced) was rejected by createConnector and updateConnector requests.

Gateway Features​

Changed​

• Login: Improve error messages when adding a new multi-factor authentication method.

Added​

• Post Processing: Add a new settlement export column fees:vat:aggregation that aggregates all mapped provider VAT fees of a transaction into a single amount.

Removed​

• Network Tokenization: Remove Network Token Metadata field (to be re-introduced in a future release).

Fixed​

• Hosted Payment Pages: Fix an issue where selecting Set as preferred payment instrument did not mark the stored payment instrument as preferred in certain scenarios.
• Post Processing Jobs: Fix net and fees total amount calculations in CAMT.053 settlement exports for transactions in different currencies.
• Risk Engine: Fix an issue where the Riskified device fingerprinting script did not load for payment.js integrations.
• User Management: Fix an issue where the Invitations tab could fail to load for administrators with access to a large number of merchants.

Gateway Adapters​

Changed​

• Adyen (ADY-EP4): Add mapping of additional card data fields from webhooks for unknown transactions.
• dLocal (DLO-EP1-CC):
  • Add a new configuration setting Expose Installment Interest to include the installment interest amount in installment options responses.
  • Add a new configuration setting chargeArgentinaInUsd to process USD transactions for Argentina.
• EBANX (EBA-EP1-PIX,EBA-EP1-UPI): Add support for cancelling Pix Automático and UPI Autopay enrollments via Deregister transactions.
• EBANX (EBA-EP1-UPI): Add support for the new payment method UPI Autopay, including enrollment with an initial payment and recurring debits. UPI Autopay is a feature of India's Unified Payments Interface (UPI) that lets customers authorize automatic recurring debits from their UPI-linked bank accounts.
• NaverPay (NAV): Add support for automated settlement data retrieval and processing.
• Paynetics (PNE): Add support for the new settlement report flow covering posting, payout, and chargeback reports.
• Stripe (STRV2): Add an optional webhookSecret configuration setting to verify the signature of incoming webhooks.

Fixed​

• Adyen (ADY): Fix an issue where outgoing callback notifications for chargeback transactions contain the wrong adapter reference ID.
• Dimoco (DIM): Fix an issue where authorization rows with a matching transaction row caused duplicate reconciliation entries.
• dLocal (DLO-EP1-PIX): Fix an issue where enrollments (register) did not support both fixed and variable subscription amounts in all enrollment flows.
• PayPal (PPA):
  • Fix settlement report processing for refunds with currency conversion.
  • Fix an issue where settlement files without a bank reference ID could not be parsed.
• Redsys (RED-EP1-CC): Fix a 3DS issue where transactions failed with a repeated order number error when the 3DS method completion arrived after the challenge had started.
• Stripe (STRV2-EP2-ACH): Fix an issue with recurring debit transactions.
• VoltUnifiedGlobalPayments (VUGP): Fix an issue where callback notifications with an unexpected status format caused processing to fail.

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​

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.