7 posts tagged with "Klarna"

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.

Features​

Changed​

• UI Navigation:
  • If the user only has access to a single connector, it is now automatically selected in the virtual terminal.
  • The last selected connector is stored locally to prevent having to re-select it for future transactions.

Added​

• BI Data Source: Scheme IDs are now available for post-processing.
• Connector Configuration: Added a new project setting, Manipulation: Field Operation that can be used to manipulate data at the connector level prior to sending the data to the PSP. It is currently possible to truncate the data after a defined number of characters using this option. More operations will be added in the future.
• Fee Management: Added the ability to specify the customer's billing state for fees.
• UI Navigation: Added information on the deployed version to both the gateway and documentation.

Fixed​

• Fee Management: Fixed an issue that would result in an error if no target fee set has been specified and the source fee set is assigned to a sub-tenant.
• UI Navigation: Fixed an issue that prevented archived jobs from being restored when in the table view.
• Virtual Terminal: Fixed an error that could occur when calculating surcharges if no credit card number has been entered.

Adapters​

Changed​

• American Express (AMX-EP1-AMX): Added support for Apple Pay.
• China UMS (UMS-EP1): Added the optional expireTime parameter to the payload. The value of this parameter is taken from the extraData field. If the parameter is not provided there, it is taken from the project settings.
• Cybersource (CYS-EP1-CC): The forwardedAcquirerCode field is now available for postback notifications.
• HypYaad (HYP-EP1-CC): Added support for settlements in CSV format and stored on an SFTP server.
• Klarna (KLW-EP1): The customer.birthDate field has been changed from required to optional.
• PXP (PXP-EP1-CC): The SchemeTransactionIdentifier, SchemeSettlementDate and DinersRetrievalReferenceNumber in callbacks are now stored for use in recurring transactions.
• SIA (SIA-E01): Added support for void and partial captures.

Added​

• Paymee (PAYME-EP1-CCRD): Paymee is a Tunisian payment gateway that accepts credit card payments via a redirect link.
• Sampath Bank (SAMPA-SVNP1-BTR): Sampath is a secure Sri Lankan online payment platform. The adapter supports bank transfers.

Fixed​

• Adyen (ADY):
  • When submitting a transaction using a hosted payment page, clicking on the back button caused the transaction to be resubmitted. This caused two transactions to be sent to the PSP, but IXOPAY only counts this as a single transaction. The duplicate transaction is automatically closed by the PSP, which can overwrite the correct transaction ID of the transaction in IXOPAY.
  • Fixed an issue with settlement notifications that caused settlements to be ignored.
• Amazon Payment Services (AMAZO):
  • A new option has been added that supports SHA-512 alongside the previously supported SHA-256 encryption. This setting should be configured in IXOPAY to match the one configured in the Amazon settings.
  • Fixed an issue generating settlement reports that would only occur when an existing settlement report was re-generated.
• China UMS (UMS): Fixed an issue that prevented the status of pending transactions from being polled correctly.
• China UMS (UMS-EP1): A refund order ID has been added, which now allows multiple refunds.
• Klarna (KLW-EP1): Fixed a number of issues that could occur in cases where the customer's birthdate is missing.
• NMI (NMI-EP1): Fixed an issue where a type error would occur if no related transaction is present and no extra data is set for a credit card connector. The expected data type is an array; if no data is available, an empty array is now used.
• Worldline (ING-EP6): Fixed an issue that could cause successful refunds to remain stuck in a pending state.

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

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​

Fixed​

• Batch Upload API: Fixed a number of issues with the Batch Upload API:
  • Fixed a bug that generated an incorrect output format when an error occurred.
  • Fixed an issue when querying the status of a batch request that would result in an HTML response being generated when the batch ID referenced a non-existent batch. A JSON response is now generated containing "batch not found".
  • In cases where validation errors (e.g. the merchantTransactionId is already assigned) prevents a transaction from being created, the transaction was not written to the output at all. The output now includes a line with success = false, along with an error message in the output file for every transaction that could not be created.
• Transaction API: Removed the thousands separator from the amount field in callbacks for transactions with a surcharge fee.

Features​

Changed​

• UI: The Tools section in the platform has been overhauled. The entries previously located here have been moved to more relevant parts of the platform - this includes options such as BitPay pairing and Tokenization.

Added​

• Job Configuration: Added a new feature to automatically add comments to potentially fraudulent transactions and send out emails with relevant information.

Fixed​

• Connector Settings: Fixed a minor visual issue that occurred when selecting the same connector setting twice. The setting was then displayed twice. The setting is now only displayed once.
• Post Processing Setting: Fixed an issue with sending callbacks for transactions created via settlements.
• Transaction List Filter: Fixed an issue with the filter for transactions created in test mode not being applied correctly.
• User Management: Fixed an issue where users were unable to add new merchant users unless they had the frontend.users.roles.edit permission.

Adapters​

Changed​

• Amazon Payment Services (AMAZO-EP1-CC): Added support for the new JSON settlement format.

Added​

• Alignet (ALI-EP01-CC): Alignet is a leading technology company based in Peru, specializing in solutions for secure electronic transactions. They pioneered the use of 3-D Secure in Latin America and are a key supplier of major banks in the region. The adapter supports credit card transactions.
• Braintree (BRA-EP1): Added support for the Blik payment method. Blik allows for bank transfers and covers all major Polish banks.
• PayTabs (PAYT-EP01-VALU): PayTabs is a payment processing solution specializing in seamless online transactions in areas such as the Middle East, North Africa and Southeast Asia. The adapter currently supports payments using the valU BNPL payment method in Egypt.
• Worldline (ING-EP2): Added a new endpoint as well as the option to switch between old and new endpoints in the configuration.
• Worldpay, checkout.com (CHE, WOR): Updated the API documentation for checkout.com and WorldPay WPG to include AVS and CVV responses.

Fixed​

• Adyen (ADY-EP3): Fixed an issue with missing notification verification for AdyenCheckout.
• Adyen (ADY-EP3-RIV):
  • Added support for partial captures for the Riverty payment method using Adyen Checkout.
  • The IP address field is now optional instead of mandatory when using the Riverty payment method with AdyenCheckout.
• Bitpay (BTP-EP1-CR): Fixed pairing issues with the new Bitpay connector configuration.
• Braintree (BRA-EP2): Fixed an issue with Braintree's Address Verification Service.
• checkout.com (CHE):
  • Fixed the handling of settlements for transactions with multiple partial captures.
  • Multiple fees are now supported for a single transaction in the settlement report.
• Klarna (KLW-EP1-APM): HTTP 400 responses are now mapped correctly.
• Mashreq (MASH-EP01): Added handling for the status "Awaited", which previously returned an error (due to this status not being documented by CCAvenue). The transaction is now set to pending when this status is received.
• MultiSafepay (MUL): Fixed an issue with the settlement fetcher that prevented settlements from being retrieved.
• Nuvei (NUV-EP2): Enabled support for partial captures.
• Zona Virtual SA - Zonapagos (ZONA-EP1):
  • A unique numeric value is now generated and sent to Zona Virtual as the payment ID Id_pago. This value is stored in the additionalId1 field in IXOPAY as a payment reference that is used if the payment fails.
  • Changes have been made to the mandatory fields. The following fields are no longer mandatory: merchantMetaData, extraData.idType, customer.identification.
  • Fixed the default error mapping.
  • Added mapping for the error when a payment cannot be found.

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.