5 posts tagged with "Customer Profiles"

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​

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.

Features​

Changed​

• Job Configuration: Strengthened TLS verification for the target host when utilizing the Send document to endpoint post-processing step.

Added​

• Connector Settings:
  • Added a new connector setting Postback/Status: include original adapter reference id in postback request and status response to enable sending extraData["originalAdapterReferenceId"] in callback requests and status responses for all transaction types.
  • Added a new connector setting Postback/Status: include reference uuid for all subsequent transactions in postback request and status response to enable sending referenceUuid in callback requests and status responses for all transaction types. This includes transactions referenced directly via the referenceUuid field, as well as related transactions in the customerProfileData.customerProfileGuid field of the customer profile, provided the customer profile belongs to the affected merchant.

Fixed​

• Customer Profiles: Fixed an issue where manually detaching a payment instrument without deleting it from a customer profile caused unwanted behavior.
• Provider Settlements and Reconciliation: The callback URL for chargebacks initiated through settlement processing is determined automatically. If the related transaction lacks a callback URL, the transaction tree is searched for an appropriate destination.
• User Management: Extended the Include Sub-Tenants filter to include sub-tenants of sub-tenants, not just direct sub-tenants.

Adapters​

Changed​

• Adyen (ADY-EP3-MBWAY): Added support for the MB Way payment method to Adyen Checkout. MB WAY, provided by MULTIBANCO, serves as a mobile wallet within Portugal's interbank payment network.
• checkout.com (CHE-EP2-IDE): Added support for the iDEAL payment method using the checkout.com NAS platform. iDEAL is an online payment method that enables consumers to pay online through their own bank. Payments are made via bank app or online banking.
• Klarna (KLW-EP1):
  • Added documentation on required parameters.
  • Added fallback logic to populate essential customer fields when shipping data is missing.
• Worldline (ING-EP2): Added support for the Sofort payment method. Sofort is the predominant online banking method in countries such as Germany, Austria, Switzerland and Belgium and continues to expand its global reach.

Fixed​

• 2C2P (2C2P-EP1): Improved the handling of empty HTTP responses received from 2C2P.
• Alignet (ALI-EP01-CC):
  • Updated documentation to clarify that customer shipping address first and last name parameters are optional.
  • Included extraData from referenced transactions in follow-up transactions.
• Bitpay (BTP-EP1): Fixed cancelUrl forwarding to Bitpay and introduced logging for Bitpay invoice adapter calls.
• Braintree (BRA): Skip loading transaction data when receiving Braintree callbacks without a paymentId.
• checkout.com (CHE):
  • Fixed an issue where settlement processing failed if a previous data fetcher returned no data.
  • Updated documentation with more detailed information about extraData fields relevant to the recipient of account funding transactions.
• Sepa Express (SEP): Improved UTF-8 handling in the account holder field to handle invalid characters more effectively.
• Unzer (UNZER-EP1): Fixed an issue with handling empty responses from the PSP.
• Volt (VOL-EP1): Enhanced callback processing to immediately mark transactions as successful upon receiving a COMPLETED status callback and the successOnSettle connector setting is enabled.
• Worldline (ING-EP2): Fixed an issue with follow-up debit transactions that reference transactions based on imported IBAN tokens.

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​

Added​

• Transaction API: Updated the API response to include the schemeReferenceIdentifier field.

Features​

Changed​

• Performance Optimization: Improved performance of the admin UI for users with many locked transactions.
• Post Processing Jobs: Added a new post-processing option that calculates the sum total for line items with the same type and details (e.g. chargebacks) in the data export. A new field, thisLineItemValue sum has been added for this purpose.

Added​

• Push Adapters: The OfflineInvoice and SepaDummy adapters now support preauthorize, register, capture, void, refund, debit and payout transactions, allowing these transactions to be included in IXOPAY.

Fixed​

• Currency Conversion: The New Deviation Tolerance button is now only displayed if the user has permission to edit deviation tolerances.
• Currency Conversion: Fixed an issue where a JSON response was received instead of an HTML page when pressing Enter while entering data for deviation tolerances.
• Customer Profiles: Fixed an issue that caused a new customer profile to be added when sending a paymentToken of an existing customer profile by supplying a transactionToken and a customerProfileData.customerIdentification in the request.
• Customer Profiles: Fixed an issue with how deleted customer profiles are handled.
• Provider Setting: Only a single rolling reserve configuration can now be defined per payment method.
• Provider Settlements and Reconciliation: The timestamp for when a transaction was last modified is now updated correctly in the settlement status.
• User Settings: Fixed permissions for merchants assigned to sub-tenants.

Adapters​

Changed​

• dLocal (DLO-EP1): Extended the dLocal adapter to support transactions in Ecuador.
• dLocal (DLO-EP1-BT): Added support for bank transfers in Costa Rica.
• Straight2Bank Pay (STRAI-E01): Added a new option checkPaymentMethod for Straight2Bank settlements that only retrieves Billdesk transactions with the status CREDITED but not with the status SUCCESS.
• Valitor (VALIT-EP1-CC): The ValitorPay adapter now supports network tokens.

Added​

• Braintree (BRA-EP1): Extended the Braintree adapter to support Venmo as a payment method.
• Braintree (BRA): Switched from a deprecated SDK version to the latest version, migrated from checkout.js to JS SDK and added support to passthrough items, shipping/billing address details, invoice ID, discounts and shipping costs.

Fixed​

• ATOM (an NTT DATA Company) (ATOM-EP1-CC): Fixed an issue that caused the signature to be calculated incorrectly if data contained special characters.
• Braintree (BRA-EP2): Updated the handling of Braintree disbursement and settlement handling to reflect the file structure supplied by Braintree for Interchange plus (IC+).
• EquensWorldline (EQW-EP2): Fixed the handling of responses using v3 of the API.
• Mashreq (MASH-EP01-CCRD): Fixed the mapping of transaction IDs in settlements for Mashreq.
• Nets Group (NETS-EP1): Fixed an issue with the Nets widget not displaying correctly on payment pages.
• Nuvei (NUV-EP1-CC, NUV-EP2-CC): Fixed an issue caused by Nuvei no longer providing the auth code in callbacks, which would cause refunds to fail.
• Nuvei (NUV-EP2): Fixed the mapping of errors to IXOPAY error codes.
• PAYONE (PASIX-EP1-CC): Added a new payment reference for Six that is valid for all countries.
• Volt (VOL-EP1): Fixed the mapping of Volt transactions in 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.

API​

Fixed​

• Provisioning API: Fixed an issue with the Provisioning API that would prevent the creation of vault connectors under specific circumstances.

Features​

Changed​

• Fee Engine: Changed the behavior for configuring GST fees to reflect the Surcharge dependencies.

Added​

• 3DS: The highest-supported 3DS version is now used where possible (i.e. 3DS v2.2.0 is used instead of v2.1.0). For more details, see 3DS 2.1.0 EOL and Changes to 3DS in IXOPAY.
• Connector Settings: A new connector setting has been added (Postback/Status: Include isAFT in postback/status response) that includes information on whether AFT was performed using this transaction.
• Post Processing: Added the ability to check whether data fetchers are set up correctly after adding or editing the data fetcher (currently only supported with the SepaExpress v1 settlement data fetcher). Results are shown in the data fetcher edit view.
• Risk Profile: Added a filter check for all transactions with a payment instrument where the doNotResubmit flag is set for the Count of transactions using same payment instrument risk rule. Added the transaction's error status (error_adapter, error_internal, cancelled, invalid) to the transaction's status selection for the Count of transactions using same payment instrument risk rule.
• Translation: Added Croatian and Slovenian to the merchant admin interface.

Fixed​

• 3DS: When external 3DS solutions are used, the values are no longer included in the postback, as IXOPAY can neither guarantee they are correct nor complete.
• Customer profiles: Fixed an issue that resulted in an incorrect wallet reference ID being entered in customer profiles.
• Multi-method connector: Fixed an issue relating to the retrieval of customer profiles when used in combination with multi-method connector.
• Search: Fixed an issue that prevented the advanced search filters from working with certain adapters.
• Transaction List: The URL included in the transaction tree on the transactions details page not link to the transactions view.
• Transactions: Fixed an issue where sending an amount without specifying a currency would set the amount to 0 for void transactions. This resulted in a full void instead of a partial void.
• UI: Fixed the tooltips in the screens used to edit connectors.
• UI: Fixed the responsive styling for the 3DS configuration, making values easier to see.

Adapters​

Changed​

• 2C2P (2C2P, 2C2P-EP1-CC): Added the option to ignore scheme fees to the settlement data fetcher configuration.
• Braintree (BRA-EP2-CC): Added support for a new disbursement file.
• Braintree (BRA-EP2-CC): The Braintree adapter now supports the new settlement file format for Myanmar.
• Checkout.com (CHE-EP1): Added the ability to configure a private key for the Checkout.com settlement data fetcher.
• DPO Pay (PAYGA-PYGT-CC): Added a new Private key parameter that can be configured at the connector level for SFTP servers.
• EquensWorldline (EQW-EP2): Changed from v2 of the API to the new v3 API.
• Mastercard Payment Gateway Services (MPG-EP1-CC): Added support for Westpac settlement file handling.
• Trustly (TRU-EP1): The response status can now be configured and failed payouts are set to FAILED.

Added​

• Straight2Bank (STRAI-E01-MPESA): The Straight2Bank adapter now supports M-Pesa as a payment method.

Fixed​

• American Express (AMX-EP1-AMX): Fixed the handling of chargebacks and chargeback reversals in settlements for American Express.
• Bank of America (BOFA-EP1-ACH): Fixed an issue that caused export errors due to missing mandatory data.
• Bank of America (BOFA-EP1-ACH): Fixed an error regarding the export of routing number extra data in the NACHA export for Bank of America.
• DOKU (DOKU, DOKU-EP01): Added support for refund transactions ini DOKU settlements.
• DOKU (DOKU, DOKU-EP01): Fixed the mapping of settlement fees and the handling of settlement amounts for the DOKU adapter.
• DPO Pay (PAYGA-PYGT): The DPO settlement parser has been updated to handle the new CSV structure of the settlement files.
• DPO Pay (PAYGA-PYG): Fixed the SFTP login to include the mandatory private key.
• Mashreq (MASH-EP01-CCRD): The default currency for the Mashreq adapter has been changed to QAR.
• PAYONE (PASIX-EP1-CC): Updated the configration for Six settlements to allow a customer-specific key to be entered.
• Redsys (RED-EP2-BIZ): Added support for HMAC_SHA256_V1 as a signature version for merchant integrations.
• Straight2Bank (STRAI-E01): Fixed the handling of refund settlements for Straight2Bank.
• Trustly (TRU-EP1): Fixed the handling of Trustly credit notification events for payouts to update the status to error and prevent chargebacks from being created.
• Volt (VOL-EP1): The bearer token status was re-added to the status request header after it was inadvertently removed.
• Volt (VOL-EP1): Updated the handling of Volt settlement files.
• Worldline (ING-EP2): Fixed a bug regarding the handling of webhooks.
• Worldpay (WOR-EP1): Fixed an issue that caused the settlement data fetcher to retrieve multiple settlements if the same settlement file was uploaded more than once.

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.