Skip to main content

15 posts tagged with "Provider Settlements and Reconciliation"

View All Tags

v24.14

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.

v.24.13

API​

Changed​

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.

v.24.12

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.

v.24.10

API​

Added​

  • payment.js: In addition to styling the CVV and card number fields on checkout pages, it is now also possible to apply styles to their placeholder text.

Features​

Changed​

  • Provider Settlements and Reconciliation: Updated the data fetcher to:
    • Validate input data
    • Inform users when the data fetcher is saved with missing or invalid data
    • Allow the data fetcher's interval to be set to 0 (no retrieval). This is now also the default value for new data fetchers.

Added​

  • Audit Log: Added the ability to export user management audit logs that includes information on users, such as the date the user was added, modified or deleted, their last login and the tenant the user is assigned to. These export logs can be found under Security Center on the Audit Log Export tab.

Fixed​

  • Documentation: Updated the Schedule API documentation to address incorrect information.
  • Documentation: Fixed an issue with the signature testing tool that would cause it to generate an incorrect signature due to a difference in how the URL path is generated compared to the IXOPAY gateway.
  • Provider Settlements and Reconciliation: Fixed an issue with chargeback reversals that would result in an error that the chargeback could not be found. This was caused by postback notifications that contain the same reference ID for both capture and preauthorization transactions.
  • Risk Profile: Fixed an issue that would prevent Starter and Growth users from editing the risk ruleset. When attempting to edit the ruleset, an error message was displayed that only one risk profile is allowed.
  • UI Navigation: Fixed an issue with Apple Pay and Google Pay transactions showing the incorrect icon for the token type.

Adapters​

Changed​

  • PAYONE (PASIX):
    • Fixed an issue with mapping fees for SIX via the E-Link adapter. New mappings have been added for the scheme fees and interchange fees to address this.
    • Updated the handling of settlements to use the current date and time as the fallback value for the payment date and settlement number if this value is not present. This was the case if the refunded amount was larger than the captured amount. Furthermore, if a payment number is available, this is used as the payment reference.

Fixed​

  • China UMS (UMS-EP1-H5): Fixed an issue with missing adapter-related data in the postback notification.
  • Paysafecard (PSC-EP1): Fixed an issue that would cause refunds to fail due to the adapter transaction ID being truncated.

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

API​

Added​

  • Transaction API: Added cardUpdateStatus and cardUpdatedAt to returnData for cardData responses when account updater is enabled.

Features​

Added​

  • Account Updater: The Payment Instruments section of Customer Profiles now shows the Status and Last Update columns for Credit Cards.
  • Meta connector: Added support for tokenizing Google Pay and Apple Pay payment information and routing these transactions to PSPs.

Fixed​

  • Post Processing Jobs: Fixed an issue with the option to pause the execution of post-processing jobs. Previously, setting the job to wait until a specific time that included seconds meant that the next strategy job was never executed.
  • Provider Settlements and Reconciliation: Settlement conflicts are now resolved as a result of the transaction being set to successful.

Adapters​

Changed​

  • Adyen (ADY-EP3-CC): Added support for post-processing Adyen settlements and reconciliation via GlobalPayments.

  • Braintree (BRA-EP1-BLI): Added support for the Blik payment method. This is a popular bank transfer payment method in Poland.

  • Redsys (RED-EP1): Added a new setting for the Redsys Bizum payment method that allows users to include an error URL in the transaction data. If the URL is specified, the system will send this URL if the payment fails, improving error handling and the user experience.

  • Worldline (ING-EP5): PostFinancePay is now available as a payment method. The following countries are supported:

    • Switzerland
    • Belgium
    • France
    • Germany
    • Netherlands
    • United Kingdom
    • Additional EU countries

    Supported currencies include CHF and EUR.

Added​

  • AllSecure (ALLSE): AllSecure is a global payment service provider that provides tailor-made online payment solutions. The adapter supports credit card payments.
  • PayPal Complete Platform (PPCP-EP1-PPE): Added a new PayPal Commerce Platform adapter. The adapter supports:
    • All transactions types using hosted payment pages
    • All transaction types by integrating PayPal directly on the merchant's website
    • PayLater capability
    • PayPal vaulting.

Fixed​

  • Adyen (ADY): Fixed an issue where lines marked as a merchant payout were not correctly mapped to the paymentReference field.
  • checkout.com (CHE-EP1-IDE, CHE-EP2-IDE): Added BIC support for transactions not involving an IBAN customer.
  • Neteller (NET-EP1): Fixed an issue where the transaction status failed to update to ERROR after receiving a postback indicating an error.
  • Worldline (ING-EP2-MAS): Fixed an issue with unformatted chargeback amounts. Due to the lack of formatting, the result was increased by a factor of 100.

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.