Skip to main content

6 posts tagged with "Transaction List"

View All Tags

v.24.16

API

Added

  • Provisioning API: Added processing:copy-customer-data-from-customer-profile-transaction to the connector settings.

Features

Changed

  • User Management:
    • Removed deprecated ACL abilities connector.WorldlineOgone.PostFinanceCard and connector.WorldlineOgone.PostFinanceEFinance.
    • Migrated existing deprecated ACL abilities to connector.IngenicoDirect.PostFinancePay.

Added

  • Connector Configuration: Add new connector setting Customer Data: Copy from customer profile transaction. If activated the shopper's information is added from the transaction that was used to create a customer profile.

Fixed

  • Job Configuration: Fixed an issue that could occur when saving Global Job Schedules.
  • Post Processing Jobs: Fixed the post-processing filter Transaction is not referenced in any job of this Job Type, ensuring it now correctly picks up transactions already collected by other job types.
  • Post Processing Jobs: Fixed the bug where the default state for newly created job schedules would be scheduled instead of Manual trigger only.
  • Transaction List: Fixed the advanced search to also filter for the meta_connector_guid when searching for transactions of a connector.
  • Transaction List: Fixed handling operators IS_EMPTY and IS_NOT_EMPTY for the advanced search.

Adapters

Changed

  • dLocal (DLO): Added support for settlement handling.
  • Klarna (KLW): Updated and restructured the documentation according to our latest guidelines.
  • PayPal Complete Payments - PPCP (PPCP-EP1-CC): Added support for the PayPal Advanced Credit Cards and Debit Card (ACDC) method.
  • PayTabs (PAYT-EP01-CCRD): Added support for the redirect credit-card payment method.
  • PXP (PXP-EP1-INST): Added support for Discover credit cards.
  • Straight2Bank Pay (STRAI): Added the configuration option daysOffset to delay data fetching a certain number of days.
  • Worldpay (WOR-EP1): Added support for chargeback handling through webhooks.

Fixed

  • Adyen (ADY-EP1, ADY-EP2, ADY-EP3): Fixes handling of second chargebacks for Adyen settlements.
  • Alipay - Ant Group (ANT-EP1-ALI): Limit retries of failed transactions to three attempts.
  • Global Payments (GBP): Fixed specifying the settlement amount.
  • PAYONE (PASIX): Fixed handling of negative fee amounts in settlements for interchange fees of refunded transactions.
  • PXP (PXP-EP1-INST): Fixed incorrectly disabled partial capture, partial void, and incremental authorization.

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.

v.24.15

API

Fixed

  • Provisioning API: Resolved an error in the Provisioning API by adding null checks when building response objects for meta connectors without a default connector.
  • Push API: Fixed handling of request bodies with invalid JSON.

Features

Changed

  • Customer Profiles: Made the action column in the customer profile payment instruments table non-sortable.
  • Transaction List: Increased the number of displayed connectors in the advanced search form from 100 to 700.

Added

  • Post Processing Jobs: Added the ability to export transaction extra data in post-processing export strategies, including "Write customized Settlement CSV", "Export Transactions to XLSX (Version 2)", "Export Transactions to XLSX", and "Export Transactions to CSV". Also, added "key" and "default" column configurations to "Export Transactions to XLSX (Version 2)", "Export Transactions to XLSX", and "Export Transactions to CSV".

Fixed

  • Account Updater: Improved the account updater to consider BIN lookup results alongside the card type for more accurate processing.
  • Account Updater: Fixed an issue in the Account Updater that caused cards to appear as updated twice in the batch for clients.
  • Connector Settings: Fixed a bug that caused the connector settings "Transactions: Expire automatically after (x) minutes" and "Expires pending transactions after given minutes" to not work when added as Global Settings.
  • Customer Profiles: Use the correct customer profile container for meta connectors.
  • Dashboard: Fixed an issue where the pivot table couldn’t resolve the connector list, causing multiple selections to show as ‘n/a’.
  • Dashboard: Fixed a dashboard issue where GUIDs were displayed instead of merchant names.
  • Hosted Payment Pages: Removed async from Google Pay JS on hosted payment pages to enable synchronous loading, ensuring the Google Pay button displays reliably.
  • Transaction List: Updated transaction list links to ensure they work correctly by including a default status, preventing 404 errors.
  • Virtual Terminal: Fixed issues in the Virtual Terminal for direct debit transactions by preventing mandate date validation when the field is empty and correcting format validation to display proper error messages instead of "unknown error".

Adapters

Changed

  • Klarna (KLW-EP1): Added a connector setting "treat the BACK status from klarna as CANCELLED".
  • Mashreq (MASH-EP01): Added support for debit auto-capture.
  • PAYONE (PASIX): Add new mappings for settlements:
    • Markup fee (condCode 701)
    • Dispute fee (condCode 55).
  • PXP (PXP-EP1-INST): Added support for the in-store card deposit payment method.
  • Sepa Express (SEP-EP3-SEP): Added support for settlement handling.
  • Worldline (ING-EP2): Always store the adapter transaction identifier if present to properly handle subsequent transactions.

Fixed

  • American Express (AMX-EP1-AMX): Fixed system trace audit number (STAN) issue by using a modulus operation on the transaction ID to ensure it fits within base36 encoding limits.
  • iyzico (IYZ): Fixed settlement handling for Iyzico to correctly parse the batch number for all settlement objects.
  • Spreedly (SPR-EP1-CC): Fixed date parsing to correctly handle microseconds included by the PSP.
  • Transbank (TRANS-TSB1): Fixed handling of empty responses.

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.

v.24.7

API

Added

  • Provisioning API: Two new fields have been added to the merchant response model: ntsEnrollmentStatus and networkTokenizationEnabled.

Features

Changed

  • Job Configuration: Information on inherited job type templates is now displayed, informing users as to why the template cannot be edited.

Added

  • Network Tokenization:
    • Information on the status of enrollment for network tokenization is now available in the base data for a merchant. A new line, "Network Tokenization" has been added. If the merchant has a TRID assigned, the status is displayed as "enabled" when viewing the data as an admin with the permission "tokenization.networkTokenization.enrollment.show".
    • Merchants can now be filtered by their NTS status in the overview.

Fixed

  • Pay-by-Link: Fixed an issue with the virtual terminal's result page not updating correctly if the initial transaction fails. Instead of displaying transaction data from the most recent (successful) transaction, data from the first (failed) transaction continued to be displayed.
  • Provider Settlements and Reconciliation: Fixed an issue that would cause chargeback reversals to be created for the debit transaction, instead of the chargeback transaction.
  • Transaction List: Fixed an issue that would cause an error in the advanced search when changing the comparison operator from a range to any other operator.
  • Transaction List: Fixed an issue with sorting credit card fields. Note that BIN data cannot be sorted.
  • User Management: The frontend.statistics.show permissions now governs access to the pivot table as well.
  • Virtual Terminal: Fixed an unhandled exception in the virtual terminal that would occur if the fee set or fee entity was not found. The exception is now handled and an empty surcharge value is returned.

Adapters

Changed

  • Adyen (ADY): The payment reference for settlements is now saved.
  • Amazon Payment Services (AMAZO): It is now possible to filter transactions by the status "Accepted".
  • MultiSafepay (MUL): Added the chargeback reason for chargebacks.
  • Stripe (STRV2-EP1-MAS): Additional data from the Stripe API response is now included in the postback's extraData.

Added

  • dLocal (DLO-EP1): Added support for the Sinpe payment method. This method supports bank transfers in Costa Rica.
  • Worldline (ING-EP2): Added support for payments via Trustly.
  • Zona Virtual SA - Zonapagos (ZONA-EP1-ZP): Added a generic payment method that redirects to the Zona Pagos payment page. The consumer can then select the desired payment method on this page to initiate the transaction.

Fixed

  • Adyen (ADY-EP3-BIZ): Fixed an issue that would cause transactions that had been processed successfully to be assigned the status error or pending.
  • checkout.com (CHE): Fixed an issue that would cause an error when retrieving the session ID.
  • eMerchantPay (EME-EP3-SEP): Fixed an error that would occur if the customer was not an IBAN customer.
  • Mashreq (MASH): Fixed an issue when checking 3DS credentials that would cause a type error.
  • Mercado Pago (MERPA-PROD): Fixed an issue with register transactions caused by the Amount For Card Verification not being included in the request to retrieve the issuer and payment method ID from the PSP.
  • Skrill (SKR-EP1): Fixed an issue related to email addresses not being tied to a Skrill account when requesting a payout. This would cause the payout to fail.
  • Volt (VOL): Fixed an issue caused by incorrectly handling errors in a response as a result.

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.

v.24.6

Features

Changed

  • Post Processing Jobs:
    • The Collect Transactions by Uploaded CSV File post-processing job now allows multiple fields (arn, uuid, and adapterTxid) to be mapped. Previously, only the arn field could be mapped.
    • A new setting has been introduced, Cascading ID Mapping. If this option is activated, IXOPAY attempts to locate related transactions for every mapped identifier (in the same order as the fields are mapped in the post-processing job). If a transaction is found, it is added to the post-processing job, while all other identifiers in the CSV are ignored for that transaction.
  • Provider Settlements and Reconciliation: Improved the error message that is displayed when a transaction cannot be found due to a missing reference in the settlement file.
  • UI Navigation: New permissions have been added that determine whether users can access the dashboard (dashboard.show and frontend.dashboard.show). Existing users and roles will automatically receive these permissions. A welcome page is now displayed as the start page for users without access to the dashboard.

Fixed

  • Fee Management: Fixed an issue that meant it was possible to save fees even when the mandatory feeStrategyParameters field did not contain a value.
  • Fee Management: Fixed an issue where the amount was incorrect in retried transactions, as the amount would include previous surcharges if the surcharge was calculated dynamically.
  • Post Processing Jobs: Fixed an issue that prevented more than 1,000 connectors from being assigned to a post-processing job schedule.
  • Provider Settlements and Reconciliation: Fixed an issue that caused the delete button to be displayed for canceled transactions. The button is now only displayed if the status of the settlement is "new".
  • Provider Settlements and Reconciliation: Fixed an issue with resolving transactions by additionalId.
  • Transaction List: Fixed an issue with sorting by card type in the Transaction List.
  • Transaction List: Fixed an issue in the Transaction List filters that would cause no results to be returned if a filter was applied to the first 8 digits of the card number.
  • UI Navigation: Fixed an issue where the red highlighting of missing reconciliations was not applied when switching pages or applying a filter.
  • Virtual Terminal: Fixed an issue with surcharge fee calculations.

Adapters

Changed

  • GoCardless (GOC-EP1): GoCardless settlements now also include payment references.

Fixed

  • Adyen (ADY): Fixed an issue caused by the Izyco settlement data fetcher configuration parameter missing the regular expression for the file name.
  • Braintree (BRA-EP1): Improved the handling of the billing address. If the extra data fields for company, first name or last name are unavailable, the company, first name and last name are taken from the Customer object.
  • checkout.com (CHE-EP1-CC, CHE-EP2-CC):
    • Fixed an issue that would cause the status of a transaction to be set to ERROR if a callback is received that is not mapped in IXOPAY.
    • The following callbacks are now handled:
      • authorization_declined
      • card_verification_declined
      • card_verified
      • authentication_started
      • authentication_approved.
    • Added the mandatory provessingChannelId parameter for the NAS platform.
  • Nexi Group (NETS): Fixed an issue with settlements caused by a missing configuration.
  • PayU (PAU-E01): Fixed an issue that would cause a backend error if the payment_id is missing in the payload during callback processing.
  • Stripe (STRV2): Fixed an issue with Stripe settlements where transactions in IXOPAY were not correctly identified.
  • Volt (VOL): Fixed an issue with retrieving settlements.

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.

v.24.4

API

Added

  • Transaction API: The "account closed" error for PCI adapters has now been mapped to error code 2001 in IXOPAY and treated as a hard decline.

Features

Changed

  • Alerts: Instead of sending out separate emails for each alert, email notifications are now sent out periodically. These emails will collect all alerts received over a time period in a single email. The default time period is 5 minutes, but can be configured individually for each notification category.

Added

  • Provider Settlements and Reconciliation: Added a new feature to allow dummy settlement files to be created in order to test various post-processing features. The "Test Settlement" option is accessible from the "Provider Settlement" page. This page has been reworked and the UI has changes as a result. A new permission, postprocessing.provider-settlement.create, has been added. This permission must be enabled in order to access the "Create Settlement", "Upload Settlement File" and "Test Settlement" actions. The old permission, postprocessing.provider-settlement.settlement-upload, has been removed. If this permission was previously active, the new permission will be active by default.

Fixed

  • Job Configuration: Fixed an issue where two Save buttons were displayed when editing job configurations.
  • Transaction List: Ignore tenant name in the transaction list if only the "Include Sub-Tenants" checkbox was checked.
  • UI Navigation: Fixed an issue where styling was not applied to conflicted transactions after applying a filter.
  • UI Navigation: Fixed issues with sorting the transaction list by cardholder, first 6-8 digits, last four digits and card type. The table can no longer be sorted by card level, card bank and card country.

Adapters

Changed

  • Neteller (NET-EP1-NET): Added support for payouts.
  • Paynetics (PNE-EP1-CC): A new data fetcher setting, "Split settlements by PayCurrency", is now available. If enabled, settlements are split by currency and the PayCurrency is used as the SettlementCurrency.
  • Skrill (SKR-EP1-SKR): Added support for payouts.

Added

  • JCC Payment Systems (JCC): JCC Payment Systems leads Cyprus' payment-processing sector, supporting merchants and financial institutions for nearly 30 years.

Fixed

  • Adyen (ADY-EP3): Disabled refunds for the Multibanco payment method, as refunds are not supported for this payment method.
  • Braintree (BRA-EP1):
    • Fixed an issue that would result in an error if the customer was empty in a transaction.
    • Fixed an issue that occurred if the public or private key were null values.
  • China UMS (UMS-EP1):
    • Fixed an issue where white space was included in requests when no customer name is provided.
    • Fixed the mapping of callback data in the extraData field.
    • Fixed an issue with integer values in the extraData. Integer values are now converted to strings.
  • Klarna (KLW-EP1): When creating a session, the merchant_reference2 field is now also included. This provides additional information for identifying the transaction.
  • Straight2Bank Pay (STRAI-E01): Fixed an issue that would occur if the encryption key and payload were missing. The system now checks whether these values are present, and a correspoing error is returned if this is the case.

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.