19 posts tagged with "Transaction Processing"

Gateway API​

Fixed​

• Transaction API: Fix an issue where expiryMonth was empty after a meta-connector failover.

Gateway Features​

Changed​

• Transaction Processing: Ensure that card details from a stored vault token take precedence over card details sent in the request.

Added​

• Apple Pay: Add the ability for merchants to add their own domains and turn off Apple Pay (Platform Mode) in the merchant settings. Accepting the Apple Pay terms and turning Apple Pay off now require a new permission.
• Network Tokenization: Add support for network tokenization of Google Pay payments with PAN_ONLY tokens.
• Post Processing Jobs: Add the setting Default Merchant for splitting jobs by merchant, so that output files without transactions are assigned to a merchant.
• Post Processing Jobs: Add filters for related captures and voids to the collect strategy Collect All Transactions (in period).
• Risk Profile: Add support for Click to Pay consumer data in risk checks.
• Risk Profile: Add support for acting on Riskified's PSD2 and 3-D Secure recommendations.

Fixed​

• Hosted Payment Pages: Fix an issue where an invalid installments value could be sent when a card had no installment options.
• Risk Profile: Fix an issue where an additional evaluation request was sent to Riskified after successful pre-authorization payments.
• Transaction Details: Fix an issue where successful failover transactions were shown with an error icon.
• Transaction Processing: Fix an issue where customers paying through a meta-connector were not redirected to the merchant's success URL after 3-D Secure in certain scenarios.

Gateway Adapters​

Changed​

• Adyen (ADY): Add the data fetcher setting processBalancePlatformTransfers to include balance platform transfers as settlement line items.
• Adyen (ADY-EP4): Add support for incremental authorization.
• American Express (AMX): Add the settlement data fetcher setting batchNumberPerPayout to create a separate settlement per payout.
• dLocal (DLO): Add the settlement setting useRequestAmountForSettlement to use the requested amount for Colombia transactions.
• DragonPay (DRA): Add support for validating RSA-SHA256 signatures on callback notifications.
• Euronet (EUR-EP1-CC): Add support for Account Verification on register requests.
• Nuvei (NUV-EP1-CC): Add support for returning the Account Name Inquiry result in the response and callback notification for register transactions.
• Payabl (P21-EP1-CC): Add support for returning the AVS result in avsResult.
• Paynetics (PNE): Add support for processing the daily fraud report to mark affected payments as fraud.
• Worldpay (WOR-EP1-CC): Add support for Visa Crypto Ramp data for crypto purchase transactions.

Fixed​

• checkout.com (CHE-EP1-CC,CHE-EP2-CC): Fix an issue with Account Name Inquiry for register transactions using business cards.
• Nuvei (NUV): Fix an issue where transactions were missing from settlements after a report column was renamed.
• PXP (PXP-EP1-INST): Fix callback notification handling for card-present captures.
• Worldline (ING-EP2): Fix an issue where card payments could remain in Redirected status after 3-D Secure in certain scenarios.

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​

Changed​

• Customer profiles API: Add the option to either detach or to detach and deregister payment instruments.
• PCI API: Add surchargeAmount, gstAmount, and totalAmount to the transaction response whenever a surcharge is present.

Gateway Features​

Changed​

• Customer Profiles: Extend the use of stored payment instruments to multi-method connectors and wallet connectors.
• Pay-by-Link: Add the ability to include values determined after payment processing (e.g. external risk check) in the result page.

Fixed​

• Network Tokenization: Fix an issue where wallet transactions were submitted for network tokenization.
• Network Tokenization: Fix an edge case where the system attempts to use a non-existent network token.
• Pay-by-Link: Fix an issue when cancelling an ongoing transaction.
• Transaction Details: Fix duplicate BIN lookup entries being added to the transaction log.
• Transaction Processing: Fix an issue where Apple Pay and Google Pay transactions could fail with an incorrect token error in certain scenarios.

Gateway Adapters​

Changed​

• Dimoco (DIM): Match fraud records (SAF + TC4) to transactions and flag them as fraud.
• Euronet (EUR): Add support for payouts.
• JPMorgan Chase (CHA): Update documentation for ACH Direct Debit.
• PayPal Complete Payments - PPCP (PPCP): Add support for multiple billing agreements between the merchant and the customer which can be configured either via connector config or extra data.
• Worldline (ING-EP5-CC): Add support for network tokens.

Added​

• MerchantE Solutions (MES): MerchantE Solutions is a US-based payment processor and gateway, enabling secure Credit Card payments for e-commerce merchants. The new adapter supports Debit, Preauthorize, Capture, Void, and Refund transaction types.
• Reflect (REF): New push adapter Reflect, a digital mobile banking app in Jordan powered by Arab Bank that offers seamless money management, digital transfers, and daily financial services.
• Upay (UPAY): New push adapter Upay, a mobile financial service in Bangladesh offering fast, secure money transfers, bill payments, and mobile recharges.
• USIO (USIO): USIO is a US-based payment processor offering integrated credit card and ACH payment solutions. The new adapter supports the payment method ACH for transaction types Debit, Register, Void, Refund, and Payout. ACH (Automated Clearing House) is an electronic funds-transfer network in the United States, enabling bank-to-bank payments.

Fixed​

• Dimoco (DIM):
  • Fix the foreign exchange gain/loss handling in the reconciliation process.
  • Fix an issue where reconciliation records are occasionally being matched to the wrong transaction due to shortened reference ids.
• eMerchantPay (EME-EP3): Fix an issue where customer data was missing on recurring transactions.
• JPMorgan Chase (CHA-EP3-ACH):
  • Fix an issue with the hosted payment page flow.
  • Fix a bug where the transaction status is prematurely set to success.

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​

Fixed​

• Transaction API: Fix an issue where callback notifications for payments using an existing customer profile did not include the customerProfileData object.
• Transaction API: Fix processing error responses to include the transaction uuid and purchaseId, and the stored API response log entry to match the response sent.

Gateway Features​

Changed​

• Transaction Processing: Improve general error mapping for declines caused by deactivated network tokens for ISO adapters.

Added​

• Post Processing Jobs: Add an optional Account Name setting to the camt.053 settlement report exporter, used as a fallback when no merchant name is available.
• Risk Profile: Add the new external risk provider Riskified. Riskified is a real-time risk management solution that uses machine learning to detect fraudulent orders and protect against chargebacks.

Fixed​

• Hosted Payment Pages: Fix an issue where the payment form did not show an error message when tokenization failed.
• Transaction Details: Fix an issue where expanding the Transaction Tree panel could show a false session-expired message and reload the page.

Gateway Adapters​

Changed​

• Klarna (KLW): Add a line item with the actual net settlement amount of each payout to the retrieved settlement data.
• PayU (PAU-E01): Add support for card payments in seven additional LATAM markets: Argentina, Chile, Panama, Costa Rica, Guatemala, Honduras, and El Salvador.
• Stripe (STRV2): Add an optional connectedAccount setting to restrict the report to a single connected account.

Fixed​

• EBANX (EBA-EP1-PIX,EBA-EP1-UPI): Fix an issue where customers were not redirected back to the shop after completing a payment and status notifications were not received.
• Klarna (KLW): Fix issues where tokenization could fail and stored customer tokens could not be used for merchant-initiated transactions.
• Nuvei (NUV-EP1): Fix an issue where merchant-initiated preauthorize transactions using stored payment data could be declined.
• Stripe (STRV2): Fix an issue where the connected account payout reconciliation report could not be generated.
• Stripe (STRV2-EP2-ACH): Fix an issue where dispute notifications for ACH Direct Debit payments were not processed.

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​

• 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.
• 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​

• User Management: Add read-only access to Global Routing Profiles and Connector Aliases, allowing users to view configurations without the ability to make changes.

Fixed​

• Dashboard: Fix an issue where the date range filter calendar in the dashboard was not responding.
• Network Tokens: Fix an issue where customer profiles did not process with network tokens.
• Provider Settlements and Reconciliation: Fix an issue where amounts in settlement export reports for CAMT.053 files could be negative.
• Transaction Processing: Fix payout responses to include merchant advice codes in the transaction result.

Gateway Adapters​

Changed​

• checkout.com (CHE-EP1-CC,CHE-EP2-CC):
  • Add documentation for the extraData.digitalGoods:type parameter for Account Funding Transfer transactions.
  • Add support for partial authorization, including the authorized amount and status, in transaction responses and callback notifications.
  • Add the network decline code and merchant advice codes to transaction responses and callback notifications.
• Dimoco (DIM): Adjustments to commission and scheme fee handling.
• dLocal (DLO-EP1-PUNTO): Add support for payments in Nicaragua via the PuntoXpress payment method.
• eMerchantPay (EME-EP2-SEP): Include the mandate reference in the callback notification for recurring direct debit transactions.
• JPMorganChase (CHA): Add a new dedicated line item to aggregate fees for disputes.

Fixed​

• Dimoco (DIM): Fix an issue where settlement files are incorrectly imported multiple times.
• Nuvei (NUV-EP1-CC): Fix an issue when using customer profile tokens for subsequent transactions.
• PayPal Complete Payments - PPCP (PPCP-EP1-CC): Fix an issue where the payment instrument was not properly registered through the hosted payment page using customer profiles.
• PayU (PAU): Fix an issue where settlement files containing dates in an alternative format were not parsed correctly.

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.