5 posts tagged with "Alignet"

Features​

Changed​

• BI Data Source: As announced, switch the BI Data Source endpoint /query/transactions from ElasticSearch to OpenSearch.

Fixed​

• API Testing: Replace username and password input fields with a user selector to reduce transmission of sensitive data.
• Customer Profile: Prevent the deletion of a customer profile’s payment instrument when deregistering a network token or PAN, even if the other was still present.
• Documentation: Update BI data source sandbox links in documentation to refer to sandboxbds.ixopay.com instead of sandbox.ixopay.com.
• Meta connector: Fix saving a routing rule node with an invalid ID or non-matching meta connector to show a proper error message instead of causing an internal error.
• Virtual Terminal: Fix internal server error in virtual terminal requests by verifying transaction object support before setting surcharge amount.

Adapters​

Changed​

• Alignet (ALI): Add support for settlement handling.
• dLocal (DLO-EP1-VPAY): Added support for the VPay QR payment method, enabling QR payments in Bolivia.
• EBANX (EBA): Add Endpoint connector configuration option to switch between Cross-border Endpoint and Local2Local (Domestic) Endpoint, with cross-border endpoint as the default.
• Nuvei (NUV):
  • Extend settlement handler to parse the new Settlement Summary Report Drill report type, selectable via the fileType field in the settlement data fetcher. Default remains Transaction Report.
  • Add automatic SFTP connection testing to settlement data fetchers.
• Payabl (P21-EP1): Update the testing endpoint to sandbox.payabl.com from sandbox.powercash21.com.
• Stripe (STRV2-EP1-CC, STRV2-EP3-CC): Add support for incremental authorization transactions for the Stripe adapter.
• Worldline (ING-EP2): Add shouldBeFinishedWhenCapturedTrustly connector setting to allow Trustly debit transactions to be marked as successful upon CAPTURED status, enabling customers to treat these transactions as finished.
• Worldline (ING-EP5): Forward transaction UUID as references.merchantReference in refund and capture requests.
• Worldpay (WOR-EP1): Add documentation for Account Funding Transactions (AFT).

Added​

• KCP Mobile (KCPMO-EP1): Add the KCP Mobile adapter with support for credit card and bank transfer payment methods. KCP Payment Solutions: Secure payment processing supporting multiple currencies and countries.
• KCP PC (KCPPC-EP01): Add the KCP PC adapter with support for credit card and bank transfer payment methods. KCP Payment Solutions: Secure payment processing supporting multiple currencies and countries.

Fixed​

• Worldline (ING-EP5): Fix a bug regarding the handling of webhooks.

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​

• 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​

Added​

• Audit Log: A color-coded diff of the changes to a post-processing job's configuration is now available.

Fixed​

• Multi-method connector: Fixed the status poll for multi-method connectors and added a new connector setting (Delay autoCapture for debits by 5min) that can be used to delay the automatic capture.
• Network Tokenization: Fixed an issue that displayed disabled merchants in the NTS enrollment and Assign TRID drop-down lists.
• Post Processing Jobs: Fixed an issue with exporting data that would cause credit card data (e.g. the brand) to be empty in the exported file.
• Provider Settlements and Reconciliation: Fixed an issue with chargeback reversals that prevented them from being processed.
• UI Navigation: The network token status tab is now hidden if no network token is available.
• UI Navigation: Fixed an issue with sorting merchants and customer profiles.
• Virtual Terminal: Fixed an issue with the formatting of surcharge amounts when entered as a percentage instead of an absolute value.

Adapters​

Changed​

• Alignet (ALI-EP01-CC): Removed the merchant transaction ID section.
• checkout.com (CHE-EP1-CC):
  • Added billing post code/ZIP and billing state fields for AFT transactions.
  • When the Postback/Status: Include Auth-Code in postback/response and status response connector setting is enabled, the auth-code sent by Checkout.com is now included in the callback.
• Cybersource (CYS-EP1-CC):
  • Added support for partial capture
  • Mapped additional fields in API calls
  • Added support for the JapanPaymentOptions parameter for installments.
• DPO Pay (PAYGA-PYGT): Added support for handling callbacks.
• Nuvei (NUV): Added the ability to parse line items containing fees in settlement files.
• PXP (PXP): An SFTP host can now be defined for the settlement data fetcher. If no SFTP host is specified, the default host (sft1.servebase.net) is used instead.
• Zona Virtual SA - Zonapagos (ZONA-EP1): Added a setting to enable custom URLs for endpoints.

Added​

• China UMS (UMS): China UnionPay Merchant Services (China UMS) is a subsidiary of China UnionPay, a major financial services corporation in China. The adapter supports payments via Alipay and WeChat Pay.

Fixed​

• Adyen (ADY-EP3): Fixed an issue with the handling of the PresentToShopper result codes with the Multibanco payment method. The transaction is now set to pending instead of causing an error. This applies to all initial transaction types (debit, preauthorize and register).
• Alignet (ALI-EP01-CC): Fixed an issue with ID duplicates caused by simultaneous transactions.
• Alipay - Ant Group (ANT-EP1-ALIPL): Fixed a rare issue where an empty response would result in an error.
• American Express (AMX):
  • Transactions in American Express settlements can now also be resolved using the additionalId1 field. The settlement handler first checks the UUID and then the additionalId1 field.
  • Refund amounts are now saved as absolute values.
• checkout.com (CHE-EP1): Fixed an issue when mapping errors where the error code is empty.
• checkout.com (CHE-EP1-IDE, CHE-EP2-IDE): Improved the adapter's error handling.
• Mashreq (MASH): Debit calls include both a preauthorize and capture call. A 5 minute delay has been added to the capture due to recurring issues with instant captures.
• Mashreq (MASH-EP01): Fixed an issue with parsing the API response that could result in an invalid value, leading to an error.
• Worldline (ING-EP2): Fixed an issue with the data type used for the mandateDate.

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.