5 posts tagged with "Callback"

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​

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.

Gateway Features​

Fixed​

• Callback: Postback notifications that previously failed due to DNS lookup issues will now be queued for retries.
• Callback: Add additional transaction logs when callback notifications fail due to DNS lookup issues.
• Fee Management: Adjust the default value for the fee configuration form to prevent unexpected configuration changes.
• Provider Settlements and Reconciliation: Fix an issue where refund transactions received via settlements were not created when the connector setting Provider Settlement: Create unknown transactions was enabled.
• Transaction List: Fix an issue where no transactions were returned when filtering by multiple UUIDs in Live mode.

Gateway Adapters​

Changed​

• 2C2P (2C2P-EP1): Update test and production endpoints.
• Adyen (ADY-EP1-CC): Map additionalData from Adyen to extraData.additionalPspResponse in API responses and callbacks (JSON-encoded) when enabled via a new connector configuration.
• Stripe (STRV2-EP1): Add support for reconciliation.
• Stripe (STRV2-EP3): Add support for reconciliation.

Fixed​

• dLocal (DLO): Treat adjustment lines as settlement meta data.

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​

• Transaction API: Added the parsedMerchantAdviceCode to transactions that contains the parsed merchant advice code for those adapters that support MAC, including the Simulator adapter.

Features​

Added​

• 3DS: The CardholderInfo field from the issuer is now returned for failed 3DS authentications. The information in this field provides additional information on why 3DS failed and can be displayed to the user.

Removed​

• Setup: Merchant and connector templates have been removed. The same functionality can now be achieved using the global settings.

Fixed​

• Callback: Fixed an issue with callbacks when the postback format was set to inherit and a follow-up transaction was using a different API version than the initial transaction.
• Post Processing: Fixed the verification of a mandatory job period setting in job schedules.
• Post Processing: Fixed an issue introduced by a recent UI update that caused some buttons to no longer work in the Post-processing configuration.
• UI Navigation: The UI has been updated to support 8-digit BINs.
• Virtual Terminal: Fixed an issue where confirmation emails were sent out incorrectly. Mails would be sent if the "vt mail on success" setting was enabled, even if the transaction was not related to the virtual terminal. Mails were also sent for all pay-by-link transactions, even if the option to send out emails for PBL was disabled.

Adapters​

Changed​

• American Express (AMX-EP1-AMX): A new setting is available for the American Express settlement data fetcher that saves the Amex payment number as the batch number, instead of using the date and time.
• Worldpay (WOR-EP1): The line item SETTLED_MISCELLANEOUS (for fees not associated with a particular transaction) is now handled without creating a conflict.

Fixed​

• 2C2P (2C2P-EP1): Fixed an issue where settlements were sometimes fetched twice.
• Adyen (ADY-EP3-APP, ADY-EP3-CC, ADY-EP3-GOP): Fixed a bug that occurred when cross-referencing a transaction at another PSP.
• Braintree (BRA-EP2): Billing address data from the initial transaction is now stored and can be used in follow-up transactions. This billing address data is now used to process debit and preauthorization transactions.
• Braintree (BRA-EP2): The field additionalId1 can now be mapped to the descriptor object, allowing the invoice number to be passed to Braintree.
• Nuvei (NUV): File names for settlements can now be entered using a new optional regular expression field.
• Volt (VOL-EP1): Fixed an issue with settlements caused by both debits and refund transactions related to the same transaction having the same ID in Volt, causing refunds to sometimes be settled instead of debits.

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.