3 posts tagged with "VoltUnifiedGlobalPayments"

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

Gateway API​

Added​

• Transaction API: Add the schemeLifecycleIdentifier and referenceSchemeLifecycleIdentifier parameters to support transaction lifecycle mandates (e.g., Mastercard TLID).

Fixed​

• Push API: Fix an issue handling an empty firstSixDigits field.

Gateway Features​

Changed​

• 3-D Secure: Add scheme logos (Visa Secure, Mastercard Identity Check, American Express SafeKey, Discover ProtectBuy, and CB FAST'R) to the 3D Secure device fingerprinting loading screen.
• Connector Settings: Allow dashes in the Target Field for the Field Expression Language connector setting.
• Meta connector: Extend the CreditcardType routing rule to support co-branded MADA subbrand cards.
• Risk Profile: Extend Forter risk engine to include additional 3DS related data.

Added​

• Connector Settings: Add new connector setting Provider Settlement: Accept from other provider GUIDs to allow transactions from different providers to be included in the same settlement.

Fixed​

• Fee Management: Fix fee calculations which are based on card region for captures and voids.
• Post Processing Jobs: Fix the display of seller names in Transaction Reports for split payments.
• Transaction List: Fix an issue where some transactions were not displayed in the transaction list.
• UI Navigation: Fix an issue that prevented filtering Admin Users when pressing the Enter key.

Gateway Adapters​

Changed​

• Adyen (ADY-EP3-MOPAY): Add support for the new payment method MobilePay, a widely used mobile wallet in Denmark and Finland that allows customers to pay using their mobile phone.
• American Express (AMX): Add a setting to map the fee type based on the discountRate: negative rate to markup-vat, positive rate to standard markup.
• Autopay (AUTO): Add support for settlement handling.
• checkout.com (CHE-EP1-CC,CHE-EP2-CC):
  • Add support for additional parameters for digital currency transactions.
  • Add a TransactionIndicatorMode setting to specify transaction indicator inference when none is provided.
• checkout.com (CHE-not-CC): Add support for Net settlements. The settlement type can now be configured as Net or Gross.
• Dimoco (DIM): Fix the settlement datetime to 12:00 PM to ensure consistent settlement timing across time zones and daylight saving changes.
• dLocal (DLO-EP1-CC): Add support for Deregisters.
• dLocal (DLO-EP1-PIX): Add support for the new payment method Pix Automático for dLocal, a Brazil‑based instant recurring payment solution that lets merchants automate authorized Pix transactions without requiring customers to approve each payment.
• HDFC CCAvenue (CCAV): Add support for settlement and reconciliation handling.
• PayPal Complete Payments - PPCP (PPCP):
  • Add support for the disableMaxWidth parameter in the SDK.
  • Include the invoice_id in Capture requests to ensure it is available in chargeback details.
• VoltUnifiedGlobalPayments (VUGP): Add support for beneficiary account identifiers (BSB, account number, and BIC) for payments in Australian Dollars (AUD).

Fixed​

• checkout.com (CHE-EP1-GOP,CHE-EP2-GOP): Fix an issue where Google Pay (PAN_ONLY) tokens processed with a provider 3DS challenge could not be used for subsequent transactions.
• DPO Pay (PAYGA-PYGT): Fix an issue where the transaction status is not updated.
• HDFC CCAvenue (CCAV): Fix an issue with response parsing.
• PayPal Complete Payments - PPCP (PPCP-EP1): Fix handling of STC (Set Transaction Context).
• VoltUnifiedGlobalPayments (VUGP):
  • Fix an issue with handling callback notifications.
  • Fix an issue with payment redirects and notification URLs.

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 Features​

Changed​

• Data Export: Improve the stability and reliability of the Data Export.

Added​

• Hosted Payment Pages: Add support for installments on the Hosted Payment Page. This feature is currently available for dLocal (DLO-EP1-CC) and Adyen (ADY-EP3-CC).
• Provider Settlements and Reconciliation: Add a setting to choose whether the receipt date or the settlement date (default) should be used for unknown transactions.

Fixed​

• Callback: Fix an issue where the schedule status (scheduleData.scheduleStatus) in callback notifications was incorrect for scheduled transactions.
• Risk Profile: Fix the Forter risk check engine script (on the HPP) to use the correct version.

Gateway Adapters​

Changed​

• dLocal (DLO): Add a setting to configure how TAX_LOCAL_AMOUNT is mapped during settlement handling - either as Scheme Fee or VAT.
• dLocal (DLO-EP1-UPI): Add support for UPI. UPI is a real-time payment system in India. This integration supports the eMandate flow, enabling the processing of recurring transactions.
• EquensWorldline (EQW-EP1-CC): Add support for network tokens.
• JPMorganChase (CHA):
  • Improve the report by displaying fees and sale amounts correctly on the same line.
  • Update the column Settled Conveyed Code to Conveyed Settled Code in the settlement retrieval file.
• Nuvei (NUV-EP1-NEQ): Add support for Nequi. Nequi is a popular mobile payment solution in Colombia that allows users to send and receive money, supporting both debit and payout transactions.
• Paynetics (PNE-EP1-CC): Add support for network tokens.

Added​

• HDFC CCAvenue (CCAV): HDFC CCAvenue is a leading payment gateway in India, enabling secure and reliable Credit Card payments via redirect. The new adapter supports Debit, Preauthorize, Capture, Void, and Refund transaction types.
• VoltUnifiedGlobalPayments (VUGP-EP1-BTR): Volt Unified Global Payments is a next-generation digital payments gateway, enabling PSD2 bank-direct payment services in Europe, the UK, and Australia. The new adapter supports Bank Transfer payments for Debit and Refund transaction types.

Fixed​

• Adyen (ADY): Add error handling for unsupported currencies.
• JPMorganChase (CHA): Fix various issues in settlement parsing to ensure data is processed correctly.
• Nuvei (NUV-EP1): Fix identifier handling to ensure refunds work correctly.
• Redsys (RED-EP1-CC): Fix the use of the reference scheme transaction identifier.
• Stripe (STRV2-EP1): Improve reconciliation handling to prevent conflicts and issues with unknown transactions.
• Stripe (STRV2-EP3): Improve reconciliation handling to prevent conflicts and issues with unknown transactions.

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.