4 posts tagged with "payment.js"

Gateway API​

Added​

• payment.js: Add support for retrieving BIN data during card number input via the getBinData option in number events.
• Provisioning API: Add a new endpoint to enroll merchants for Network Tokenization.
• Push API: Add support for the items field for Debit, Preauthorize, Capture, Refund, and Payout transactions.
• Transaction API: Add support for submitting partial authorization data in the transaction request payload.
• Transaction API: Add support for submitting unlinked refund data in the transaction request payload.

Gateway Features​

Changed​

• Transaction Processing: Forward the Scheme Lifecycle Identifier from the initial transaction in follow-up Debit and Preauthorize requests. Optionally include it in API responses and callback notifications via the connector setting Postback/Status: Include schemeLifecycleIdentifier in postback/status response.

Added​

• Meta connector: Add a new routing rule that allows routing based on the adapter and payment method used during the initial registration, enabling cross-tenant recurring payment routing.
• Post Processing Jobs: Add a new Fee Conversion setting to the CAMT053 export strategy, allowing transaction amounts to be converted to a specified target or fixed currency in the export.
• Post Processing Jobs: Add the Payout Reference to all entries in the CAMT053 XML export, omitting the field when no reference is available.
• Post Processing Jobs: Add transaction split data to the transaction data export.
• Post Processing Jobs: Add new settings to the CAMT053 export strategy to include fee-only transactions and balance transfer entries derived from job line items in the export.
• Post Processing Setting: Add a new provider setting to enable settling unreferenced refund (payout) transactions as refund transactions.
• Transaction Details: Add split transaction details to the transaction detail view.

Fixed​

• BIN Lookup: Fix an issue where an Apple Pay Preauthorize transaction with no BIN lookup data followed by a Capture caused an error.
• Blocklist: Fix an error in the automatic block list triggered when a transaction had an empty credit card fingerprint or BIN value.
• Callback: Fix an issue where callback notifications were sent in the wrong format for connectors configured to use V3 SHA512 signing.
• Customer Profiles: Fix an issue affecting customer profiles when transactions fail over to another connector.
• Post Processing Jobs: Fix the amount calculation for Refund and Chargeback transactions in the CAMT053 XML export.
• Post Processing Jobs: Fix an issue where the Collect Transactions from Related Batch strategy did not collect transactions settled via a different provider when the Provider Settlement: Accept from Other Provider GUIDs setting was enabled.
• Virtual Terminal: Fix an issue where Preauthorize and Register transactions made via the Virtual Terminal were not flagged as MOTO.

Gateway Adapters​

Changed​

• Dimoco (DIM):
  • Add automatic calculation and isolation of foreign exchange gain/loss amounts in settlement processing, with an option to segment results by card scheme.
  • Add support for SAP settlement files, mapping them to the correct settlement batch based on the day of the week.
  • Add support for processing CBE entries in TK011 settlement files.
• EBANX (EBA-EP1-PIX): Add support for enrollment to facilitate recurring transactions.
• HDFC CCAvenue (CCAV-EP01-CCRD): Improve transaction status verification.
• Straight2Bank Pay (STRAI-E01-CC): Add support for card payments via redirect.
• Straight2Bank Pay (STRAI-E01-QRIS): Add support for the new payment method QRIS. QRIS (Quick Response Code Indonesian Standard) is Indonesia's unified QR code payment standard, enabling customers to pay by scanning a single QR code using any participating Indonesian bank or e-wallet application.
• Straight2Bank Pay (STRAI-E01-VAIND): Add support for the new payment method Virtual Account (VA). Virtual Account is a widely used payment method in Indonesia where customers complete payments by transferring funds to a unique, dynamically assigned bank account number.
• Worldline (ING-EP2-BTR): Add support for resolving the transaction reference from nested callback notification payloads for payment and refund callbacks.

Added​

• Aeropay (AERO): Aeropay is a US-based payment network that enables instant bank-to-bank transfers for direct ACH payments. The new adapter supports Register, Debit, Preauthorize, Capture, Void, Refund, and Payout transaction types. Aeropay allows customers to pay directly from their bank account without a credit or debit card, using a one-time MFA confirmation during the registration flow.
• Connexpay (CXP): ConnexPay is a leading payment provider in the United States and Europe, enabling secure and reliable credit card payments. The new adapter supports Debit, Preauthorize, Capture, Void, and Refund transaction types.

Fixed​

• Dimoco (DIM):
  • Fix an issue where settlement records were not processed when the primary transaction identifier was missing.
  • Fix a reconciliation issue that occurred when the card scheme split configuration was disabled.
• JPMorganChase (CHA): Fix an issue where settlement files could be fetched and processed more than once.
• PayPal Complete Payments - PPCP (PPCP-EP1-PPE): Fix an issue where the billing city and billing state were mapped incorrectly in payment requests.
• PayU (PAU): Fix an issue where statement files were downloaded and processed multiple times during post-processing.

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​

Added​

• payment.js: Add support for ARIA attritbutes for card number and security fields.
• Post Processing Jobs: Display seller names in Transaction Reports for split payments.

Fixed​

• Multi-method connector: Fix failover transactions with customer profiles.

Gateway Adapters​

Changed​

• Adyen (ADY-EP3-MOPAY): Add support for the new payment method MobilePay. MobilePay is a popular digital wallet in Denmark and Finland, enabling customers to pay securely via a mobile app linked to their payment card or bank account.
• Autopay (AUTO-EP1): Add support for Customer-Initiated Transactions (CIT) and Merchant-Initiated Transactions (MIT).
• dLocal (DLO-EP1-AOZ): Add support for the new payment method Virtual Accounts Japan. This payment method facilitates bank transfers using either Dynamic Virtual Accounts (unique per transaction) or Static Virtual Accounts (assigned per merchant/customer), enabling automated and accurate reconciliation for Japanese payments.
• dLocal (DLO-EP1-BRE): Add support for the new payment method Bre-B. Bre-B is Colombia's national instant payment system, allowing customers to pay directly from their participating bank app or digital wallet by scanning an interoperable QR code.
• dLocal (DLO-EP1-CAPI): Add support for the new payment method Capitec Pay. Capitec Pay is a South African payment solution that enables customers to pay securely and directly from their bank account by authenticating the transaction via the Capitec banking app.
• dLocal (DLO-EP1-QRARG): Add support for the new payment method QR Interoperable Argentina. QR Interoperable is a solution based on the Transferencias 3.0 initiative, enabling customers to pay by scanning a single, standardized QR code using any compatible banking app or digital wallet in Argentina.
• dLocal (DLO-EP1-QRIS): Add support for the new payment method QRIS. QRIS (Quick Response Code Indonesian Standard) is a unified QR payment system regulated by Bank Indonesia, allowing customers to pay using any supported e-wallet or banking app by scanning a single code.
• dLocal (DLO-EP1-THAI): Add support for the new payment method Thai QR Payment. Thai QR Payment is Thailand’s national QR standard, enabling instant, cashless payments by scanning a code from any compatible mobile banking application.
• dLocal (DLO-EP1-VAIND): Add support for the new payment method Virtual Accounts Indonesia. This digital payment method assigns a unique virtual account number to each customer, allowing them to complete transactions via bank transfer using their preferred Indonesian banking app or ATM.
• dLocal (DLO-EP1-VNP): Add support for the new payment method VNPay-QR. VNPay-QR is a widely used payment solution in Vietnam, allowing customers to pay securely by scanning a QR code directly from supported mobile banking apps and e-wallets.
• GoCardless (GOC): Update documentation.
• GoCardless (GOC-EP1-BTR): Improve error mapping.

Added​

• JPMorganChase (CHA): Fix settlement validation logic to correctly handle optional fields based on the transaction type.

Fixed​

• Bangkok Bank (BB):
  • Fix parsing of negative refund amounts in settlement files.
  • Fix mapping of the net settlement amount to use the net payout value instead of the gross amount.
• Dimoco (DIM): Add support for processing TK011 and TK012 settlement files.

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​

• payment.js: Updated the version of jQuery used in payment.js to 3.7.1.

Added​

• BI Data Source: Introduced BI Data Source API v2 built on OpenSearch for improved performance and functionality.

Features​

Changed​

• Job Configuration: A new column has been added to the "Write customized Settlement CSV" export step, relatedFirstTransactionUuid.

Added​

• Audit Log: Audit logs are now available for providers. These logs include changes to the provider ID, data fetcher and configuration changes.

Fixed​

• Callback: Fixed an issue where notifications for partial refunds were sometimes mapped to the wrong refund transaction.
• Post Processing Jobs: The "Write customized Settlement CSV" job step included two columns that accessed the UUID of the related transaction (referenceTxUuid and referenceUuid). referenceTxUuid has therefore been removed.
• Post Processing Jobs: Fixed an issue that would cause an error if no provider was entered in a connector.
• Provider Settlements and Reconciliation: When processing a settlement file, the meta-connector for a transaction is now set correctly if a meta-connector is used by the related transaction.
• Provider Settlements and Reconciliation: Fixed an issue that would occur when creating new transactions from a settlement.
• Provider Settlements and Reconciliation: Fixed an issue caused by restricting the allowed ports in the SFTP receiver.
• Virtual Terminal: Fixed an issue that could occur if surcharge and GST fee calculation permissions were granted, but only surcharges were configured in the virtual terminal.

Adapters​

Changed​

• Braintree (BRA-EP1): The merchant account ID has been added to the configuration used in the setup process to improve the integration. This ensures that transactions are correctly associated with the relevant merchant account.
• Klarna (KLW-EP1-APM): Added support for the following countries:
  • Czechia
  • France
  • Greece
  • Hungary
  • Ireland
  • Italy
  • Poland
  • Portugal
  • Slovakia
  • Romania
  • Spain.
• PXP (PXP-EP1):
  • Added support for the Aircash and Aircash Abon payment methods.
  • Added support for payout with redirect.
• Simulator: Updated the documentation to cover overriding the outcome.

Fixed​

• Alignet (ALI-EP01-VIS): The phoneCode and phoneSubscriber fields are no longer mandatory.
• Klarna (KLW-EP1):
  • Fixed an issue in the documentation regarding the shipping email and total discount amount. customer.shippingEmail has been corrected to customer.extraData.shippingEmail and items.item.totalDiscountAmount has been changed to items.item.extraData.totalDiscountAmount.
  • Fixed an error that would occur if a request timed out. This was caused by the empty response not being handled correctly.
• Mashreq (MASH): Fixed an error caused by unknown transactions in the postback.
• Sepa Express (SEP-EP3): Fixed an issue that would cause an error if the connectorId is missing when creating a mandate. The system now checks that this required value is present.
• Worldline (ING): The SFTP password is no longer mandatory, as the setup is switching over to using a private key.

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​

• payment.js: In addition to styling the CVV and card number fields on checkout pages, it is now also possible to apply styles to their placeholder text.

Features​

Changed​

• Provider Settlements and Reconciliation: Updated the data fetcher to:
  • Validate input data
  • Inform users when the data fetcher is saved with missing or invalid data
  • Allow the data fetcher's interval to be set to 0 (no retrieval). This is now also the default value for new data fetchers.

Added​

• Audit Log: Added the ability to export user management audit logs that includes information on users, such as the date the user was added, modified or deleted, their last login and the tenant the user is assigned to. These export logs can be found under Security Center on the Audit Log Export tab.

Fixed​

• Documentation: Updated the Schedule API documentation to address incorrect information.
• Documentation: Fixed an issue with the signature testing tool that would cause it to generate an incorrect signature due to a difference in how the URL path is generated compared to the IXOPAY gateway.
• Provider Settlements and Reconciliation: Fixed an issue with chargeback reversals that would result in an error that the chargeback could not be found. This was caused by postback notifications that contain the same reference ID for both capture and preauthorization transactions.
• Risk Profile: Fixed an issue that would prevent Starter and Growth users from editing the risk ruleset. When attempting to edit the ruleset, an error message was displayed that only one risk profile is allowed.
• UI Navigation: Fixed an issue with Apple Pay and Google Pay transactions showing the incorrect icon for the token type.

Adapters​

Changed​

• PAYONE (PASIX):
  • Fixed an issue with mapping fees for SIX via the E-Link adapter. New mappings have been added for the scheme fees and interchange fees to address this.
  • Updated the handling of settlements to use the current date and time as the fallback value for the payment date and settlement number if this value is not present. This was the case if the refunded amount was larger than the captured amount. Furthermore, if a payment number is available, this is used as the payment reference.

Fixed​

• China UMS (UMS-EP1-H5): Fixed an issue with missing adapter-related data in the postback notification.
• Paysafecard (PSC-EP1): Fixed an issue that would cause refunds to fail due to the adapter transaction ID being truncated.

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.