9 posts tagged with "Post Processing Setting"

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​

• Provider Settlements and Reconciliation: Add ability to manually upload reconciliation files.

Fixed​

• Post Processing Setting: Fix a bug where setting a provider's adapter to - caused an error.
• Transaction Processing: Improve handling of follow-up transactions to prevent errors after deregistration.

Gateway Adapters​

Changed​

• Adyen (ADY): Improve error mapping to consider the reason value when provided.
• Adyen (ADY-EP4): Add documentation for referenced and unreferenced Refunds.
• Certegy (CERTE-EP1-ACH): Fix Register and Refund handling.
• DPO Pay (PAYGA-PYGT): Add support for Partial Refunds.
• PPRO (PPR-EP1): Update the endpoint from https://api.girogate.de to https://simpleapi.ppro.com.

Fixed​

• Adyen (ADY-EP3): Fix an issue where extra data was not forwarded for Refunds.
• Bangkok Bank (BB): Fix handling of negative VAT values for settlements.
• dLocal (DLO): Fix an issue with parsing settlement files.

iFrame​

Added​

• UT iFrame: Export TypeScript types from main entry point for standard importsConfiguration, Authentication, HMACAuthentication, and other key types now available. Resolves issue requiring non-standard import paths from node_modules.

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.

Features​

Changed​

• Post Processing Setting: Added validation of custom parameters, it will now show an error when trying to save post processing job settings with invalid custom parameters.

Fixed​

• Customer Profiles: Use the network token (dPAN) instead of the fPAN when a customer profile was created or updated from a network token registration.

Adapters​

Changed​

• Valitor (VALIT): Added support for mapping Acquirer Reference Numbers (ARNs) in settlement processing.
• Worldpay (WOR-EP1): Added support for account funding transactions (AFT).

Fixed​

• GoCardless (GOC): Fixed an issue in settlement processing where missing links.payment or links.refund in a refund object would previously cause an error and stop transaction retrieval.
• Klarna (KLW): Fixed Klarna settlement configuration to allow longer passwords via the KlarnaApiPassword field in the provider settlement data fetcher configuration. If no KlarnaApiPassword is set, the connector configuration password will still be used.
• Nexi Group (NETS): Fixes a problem with the test-mode configuration setting which prevented retrieving settlements.
• PayPal Complete Payments - PPCP (PPCP-EP1-PPE): Removed null values from the setup token call to prevent issues with the prepare-register call when shipping details are not provided.
• PXP (PXP-EP1-INST):
  • Added missing adapter specific documentation.
  • Send initiatePaymentFromReferenceRequest.merchantTransactionId to the PSP to correctly link follow-up transactions with their initial transaction.
  • Fixed handling of responses of capture, refund, and void transactions.
• Worldpay (WOR-EP5): Fixed the settlement amount calculation for refunds during settlement 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.

API​

Changed​

• Provisioning API: Added the field eventNotificationUrl to merchant entities.
• Transaction API: Added field transactionSubType to the status API calls and to transaction callback bodys.

Features​

Changed​

• BIN Lookup: Updated the BIN data source.
• Pay-by-Link: Introduced a new pay-by-link-enabled permission to allow control over which API users can trigger pay-by-link transaction., The permission defaults to enabled for existing API users who have previously used pay-by-link, and disabled for all others.
• Transaction Processing: Enabled sending transaction descriptions to upstream PSPs for void and capture transaction types.

Added​

• Account Updater (Network Tokenization): Added a notification service that sends callbacks to shared merchants —those sharing a customer profile container— whenever a transaction is updated through the account updater or NTS Updates.

• Fee Management: Added a new field Transaction Subtype to Fee Constraints, including it in fee calculations; subtypes can be Chargeback Resolved, Chargeback Reversal Resolved, or - any - for no specific preference. Fee items will now be grouped by transaction type and subtype (if present).

• Job Configuration: Introduced transaction subtype filtering to the following Collecting Post Processing Job steps:

  • Collect Transactions from Related Batch
  • Collect All Transactions within a Period
  • Collect Transactions from Provider Settlements (created/settled within a period)
  • Collect Transactions by Settlement State

  Introduced transaction subtype filtering and grouping to the following Processing Post Processing Job steps:

  • Aggregate Transaction Fees to Job Line Items
  • Aggregate Transaction Values to Job Line Items
  • Calculate Rolling Reserve for Merchant
  • Count Transaction Value to Job Line Items.

• Post Processing Jobs: Added support for filtering via the transaction subtype in the transaction view for Post Processing Jobs.

• Post Processing Jobs: Added transaction subType column as possible export value for the following Post Processing Job steps

  • Export Transactions to CSV
  • Export Transactions to XLSX
  • Export Transactions to XLSX (Version 2)
  • Write customized Settlement CSV.

• Provider Settlements and Reconciliation: Added support for filtering via the transaction subtype in the Transactions in Batch and Conflicted Transactions views for Provider Settlements.

• Transaction Details & Post Processing Jobs & Provider Settlements and Reconciliation: Added subtype to the transaction Details view.

• Transaction Processing: Added a subtype field to transactions for rapid dispute resolution, with available subtypes "chargeback resolved" and "chargeback-reversal resolved".

Fixed​

• Post Processing Setting: Set a default transaction type when creating transactions derived from settlements without a transaction type.
• Transaction Details: Fixed an issue where displaying Risk Data on the Transaction Detail page could cause an error in certain cases.
• Virtual terminal: Fixed the virtual terminal view for merchant users.

Adapters​

Changed​

• Amazon Payment Services (AMAZO-EP1): Added clear error messages for transactions when errors are triggered by incoming postbacks.
• MultiSafepay (MUL-EP1): Added Content-Type: application/json to requests sent to the PSP to ensure the PSP can look-up the requests in their logs.
• Valitor (VALIT): Added support for RDR.

Added​

• Bangkok Bank (BB): Added the Bangkok Bank post processing adapter with support for settlement handling.

Fixed​

• Global Payments (GBP): Resolved a bug in the parsing of Global Payments settlements.
• GoCardless (GOC-EP1): Removed mandate callback handling for cases where the initial registration was already successful.

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​

• BI Data Source: BREAKING CHANGE BI Data Source API v1 is deprecated and will be removed in a future release. We strongly recommend migrating to v2 as soon as possible.

Fixed​

• Pay-by-Link API: Fixed an issue that would prevent a pay-by-link transaction from being canceled if a failover occurred for the transaction.
• Push API: Fixed an issue that would cause a type error if an empty body request was submitted in a Push API request.
• Transaction API: Fixed an issue where invalid 3DS values (browserColorDepth, browserTimezone) sent to the API in transaction data would cause an error. These invalid values are now ignored.

Features​

Changed​

• Connector Settings: The "Postback: Include 3DS Data" connector setting is now also available in the global settings.
• Post Processing Jobs: Optimized the process of collecting transactions in post-processing jobs.
• UI Navigation: Improved the parent tenant selection when creating a new tenant. By default, the current tenant is set as the parent tenant and the drop-down is now searchable.
• UI Navigation: Updated risk logs so that they are loaded asynchronously. This improves the initial load time for the transaction details view. Risk data is now only loaded when expanding the view.

Added​

• Connector Configuration: Added audit logs for the "Additional Configs" in the connector view.

Fixed​

• Audit Log: Fixed an issue that would cause an error when accessing the audit log if the corresponding merchant cannot be found when checking access permissions.
• Fee Management: Fixed an issue that would cause an error when changing the mapping to a different fee entity. The mapping for the old fee entity is now removed, and the mapping is set to the new fee entity.
• Post Processing Setting: Fixed an issue with the "Create unknown transaction on connector with GUID" option for settlements that prevented unknown transactions in a settlement file from being added to the platform.
• Provider: Fixed an issue that would occur when saving a connector configuration. Previously configured connectors that were assigned to the same provider were removed when the configuration was saved, with only the new configuration linked to the provider.
• Provider Settlements and Reconciliation: Fixed an issue that would cause an error when trying to sort missing reconciliation data by merchant.
• Risk Profile: Fixed an issue where saving a risk rule without entering parameter values would result in a type error.
• Risk Profile: Fixed an issue that would cause an error when opening risk rules if the risk rule set ID referenced a risk rule set that does not exist. A 404 error is now displayed instead.
• Transaction Processing: Fixed an issue caused by the platform attempting to collect 3DS information for Apple Pay transactions. The system now checks whether a transaction uses Apple Pay before collecting additional 3DS information.
• UI Navigation: The loading page displayed for the collectMissing3DSecureData connector configuration was only displayed in English. The page is now displayed in the language of the transaction where available, with English as the fallback language.

Adapters​

Changed​

• American Express (AMX-EP1-AMX): Added a new gateway connector configuration option, "Force System Generated STAN". This option can be used to force the system trace audit number (stan) to be generated by the IXOPAY platform and stored in the additionalId1 field. The following options are available to determine the format of the STAN:
  • "Yes - Uppercase characters only"
  • "Yes - Upper- and lowercase characters".
• Banca Intesa (BAI-EP1): If the PSP includes the TRACEID in a transaction response, it is now included in the postback.
• Braintree (BRA-EP1-BLI): Added support for partial refunds for the Blik non-redirect payment method.
• Braintree (BRA-EP1-PPE): Added support for line items and a corresponding option, includeLineItems has been added to the connector configuration.
• dLocal (DLO-EP1-CC): The merchantTransactionId is now passed to the vault, in order to pass it on to the PSP in refund requests.
• HypYaad (HYP): Removed the mapping of payment references in settlement files, as this could lead to a single settlement file being split into multiple settlements.
• Mastercard Payment Gateway Services (MPG, BAMI): Added support for the scheme transaction ID.
• Nexi Group (NETS-EP1): Added support for specifying the language in the checkout payload for transactions. This ensures that the language field is included in the payload if it is included in the transaction's extra data.
• PayPal (PPA-EP1-PPE): Added the isFinalCapture flag for capture transactions. If set to true, the capture is marked as final on the PayPal side and no further captures are possible.
• Simulator: Added support for incremental authorization for simulated credit card transactions.

Added​

• WavePay (WAV): The WavePay push adapter allows cash collection payments to be pushed to the IXOPAY platform to ensure that these transactions are also available within the system.

Fixed​

• Afterpay (AFT): Fixed an issue with retrieving the minimum/maximum price, caused by a missing interface.
• American Express (AMX-EP1-AMX): Fixed an issue that would cause an error if settlement files are not formatted correctly.
• Braintree (BRA): If rows in a settlement file did not include a settlement date, the settlement date was previously taken from the first value found in the "Settlement Date" column of the file. However, this could result in the settlement date being incorrect. The behavior has therefore been changed to set the settlement date to the transaction's disbursement date instead.
• Braintree (BRA-EP1-PPE): The merchantAccountId is now only passed to Braintree's JavaScript SDK if a value is present.
• iyzico (IYZ):
  • Fixed an issue with that would cause the batch number to be set to the entire file name of the settlement file, rather than the initial numerical portion of the file name. This was caused by empty rows in the settlement file.
  • Fixed an issue that would cause some settlement files to be parsed incorrectly.
• Khipu (KHI): Fixed an issue with retrieving the bank list, caused by a missing interface.
• Klarna (KLW): Fixed an issue that would result in the error "Invalid Response" being returned for transaction without a body. An empty body is now handled correctly, with the HTTP error code being checked prior to parsing the response.
• Mashreq (MASH-EP01): Fixed an issue where the status of successful transactions was not set correctly due to the status in the response not being formatted as expected.
• Payabl (P21): Fixed an issue caused by the error code parameter being evaluated incorrectly.
• Paymee (PAYME-EP1-CCRD): Fixed an issue where refund amounts would be sent with a varying number of decimal places, which could sometimes lead to errors. Refund amounts are now formatted consistently.
• Trustly (TRU): Fixed an issue that would cause a generic payment error if the private key required to generate the signature was missing. The system now checks for its presence.

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.