Skip to main content

23 posts tagged with "Transaction API"

View All Tags

Gateway — v26.20

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 — v26.17

Gateway API​

Changed​

  • Provisioning API: Update the business identification validation to accept Brazil's new alphanumeric CNPJ format.

Added​

  • Transaction API: Add the adapterMerchantTransactionId field to record the PSP's merchant transaction identifier for transaction matching and reconciliation.

Gateway Features​

Changed​

  • Post Processing Jobs: Add a preciseSettlementExchangeRate column with the unrounded settlement exchange rate to Write Customized Settlement CSV and Write Settlement CSV with Split Transaction Merchant.
  • Post Processing Jobs: Add a Fee Conversion setting to Write Customized Settlement CSV that converts aggregated fee sums into the settlement currency, with matching currency columns for each fee aggregation.
  • Risk Profile: Add support for reporting a specific cancellation reason to Riskified on void and refund requests.

Added​

  • Audit Log: Add audit log entries for manually performed void, capture, and chargeback actions, including chargeback reversals.
  • Connector Settings: Add a connector setting that lets you specify which customer fields are stored when a customer profile is created during transaction processing.
  • Customer Profiles: Add support for sharing stored payment instruments with multi-method meta connectors and with wallet connectors using the same payment method.
  • Risk Profile: Add a new risk rule that blocks payout transactions once their cumulative volume exceeds a configured daily, weekly, or monthly limit.
  • Risk Profile: Add a per-rule setting to automatically void or refund a transaction that Riskified flags as declined, instead of requiring manual action.
  • Transaction Details: Add the option to show which user manually created a transaction on the transaction detail page.

Fixed​

  • Connector Configuration: Fix an issue where a connector's terminal could not be edited when the terminal ID contained special characters.
  • Customer Profiles: Fix an issue where a deregister could point at the connector it was received on instead of the correct one.
  • Fee Management: Fix an issue where gateway fees could display the wrong label.
  • Post Processing Jobs: Fix an issue where SFTP export jobs rejected custom ports that were already approved for use.
  • Risk Profile: Fix an issue where partial voids and partial refunds were reported to Forter as canceling the order instead of reflecting the remaining total.
  • Risk Profile: Fix an issue where shipping cost data could be missing from Riskified risk checks run after the transaction was authorized.

Gateway Adapters​

Changed​

  • checkout.com (CHE-EP2-CC): Add support for forwarding device fingerprint data via the extraData.device_session_id field for Debit, Preauthorize, and Register transactions.
  • Dimoco (DIM): Add support for parsing Mastercard SAFE fraud advisory records from settlement files.
  • Nuvei (NUV-EP1-WCP): Add an option to include additional customer details with WeChat Pay debit transactions.
  • Worldline (ING): Add support for reading Visa TC40 fraud alerts from the daily fraud report file.

Added​

  • Fiserv (FSV-EP1-CC): Fiserv Commerce Hub is a global payment processing platform from Fiserv, enabling secure Credit Card payments. The new adapter supports Debit, Preauthorize, Capture, Refund, and Register transaction types.

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 — v26.15

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 — v26.11

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 — v26.9

Gateway API​

Changed​

  • Transaction API: Add adapter name and brand to tracing data (includeTracing).

Added​

  • Batch-upload API: Introduce Batch Upload API V2.
    • Support for deregister transactions.
    • A new lenient processing mode that skips invalid rows instead of aborting the batch.
    • A structured JSON result file.
    • Dedicated endpoints for status polling, result download, and batch listing.

Fixed​

  • Push API: Fix an issue where the provider was not assigned to transactions.

Gateway Features​

Added​

  • Customer Profiles: Add the ability to exclude specific stored payment instruments on the payment selection page.
  • Meta connector: Add a new routing rule which allows routing to specific card networks.

Fixed​

  • BI Data Source: Fix an issue where network token status changes were not reflected in the BI Data Source.
  • Post Processing Jobs: Fix an issue where the transaction count in the Transactions tab of a post-processing job could be lower than the actual number of transactions.

Gateway Adapters​

Changed​

  • Adyen (ADY-EP3-CC): Update response mapping documentation for AVS and CVV.
  • Autopay (AUTO): Add rolling reserve line items to settlements, distinguishing between deducted reserve amounts and payout amounts.
  • checkout.com (CHE-EP1-CC,CHE-EP2-CC): Add support for unreferenced refunds.
  • dLocal (DLO-EP1-CC): Add a configuration setting to set a default transaction indicator for register transactions.
  • dLocal (DLO-EP1-NETIN): Add support for the new payment method NetBanking. NetBanking is a popular bank transfer method in India that supports recurring payments, allowing customers to securely authorize a mandate for future subsequent transactions.
  • Klarna (KLW): Add a sendReferenceInCaptures configuration setting to include the transaction UUID in capture requests for reconciliation purposes.
  • PayPal (PPA): Add support for retrieving settlement reports from the sandbox environment when the connector is in test mode.
  • PPRO (PPR-EP1-EPS): Add support for reversal handling.
  • PPRO (PPR-EP1-IDE): Add support for reversal handling.
  • PPRO (PPR-EP1-TWI): Add support for the new payment method TWINT. TWINT is the leading mobile payment method in Switzerland, allowing users to complete transactions instantly either directly in the smartphone app or by scanning a QR code.

Fixed​

  • Autopay (AUTO-EP1): Fix register requests in migration flows to inherit the transaction indicator from the original transaction.
  • HUA NAN COMMERCIAL BANK (HNCB-EP1-CCRD): Fix transactions failing due to a transaction reference exceeding the maximum field length.
  • Redsys (RED-EP2-BIZ): Fix an issue where payment cancellations were routed to the error URL instead of the cancel URL.

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.