8 posts tagged with "dLocal"

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​

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.

API​

Changed​

• BI Data Source: BREAKING CHANGE BI Data Source API v1 is deprecated and will be removed in a future release. We strongly recommend migrating to v2 as soon as possible.

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.

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.

API​

Fixed​

• Transaction API: Fixed an issue where adapter error codes (errors.adapterCode) were sometimes returned as a numeric value instead of as a string.

Features​

Changed​

• Connector Configuration: When adding a connector or meta-connector, the public integration key is now prefilled with a random valid value. This value can still be edited and realtime feedback is provided on whether the edited value is valid.
• Connector Settings: Ensured referenceUuid is present in all cases when the connector setting Postback/Status: include reference uuid for all subsequent transactions in postback request and status response is enabled.
• Virtual Terminal: The virtual terminal has been reworked, including the Transaction, Customer, Credit Card and Payment details sections. New permissions have been introduced to handle the new streamlined form. Some of the business logic has been reworked or extended and GST calculations are now included in the Transaction section. The type of transactions available in the virtual terminal can now also be restricted using a new tenant/connector setting. For more information, refer to the User Manual.

Added​

• Connector Settings: Added a new connector setting Postback/Status: Include captureId for debit transactions in postback request and status response if available to enable sending captureId in callback requests and status responses.

Fixed​

• BI Data Source: Fixed the recurring status for chargeback and chargeback reversal transactions in the BI data source.
• Post Processing Jobs: Fixed an issue that would cause an error if the ID for a post processing job schedule was incorrect.
• Post Processing Jobs: It is now possible to add static values to aggregated lines in CSV exports by defining a default value for the static column field.
• Provider Settlements and Reconciliation: Settlements can now be resolved using all available IDs.
• Provider Settlements and Reconciliation: When assigning a connector to a provider, it is now possible to view and select the connectors for these merchants assigned to sub-tenants.
• User Management: Fixed an issue that could result in an error when a user attempts to change their password. In such cases, users are now redirected to the login page instead.

Adapters​

Changed​

• Adyen (ADY-EP1-CC, ADY-EP3-CC): Added support for network tokenization.
• dLocal (DLO-EP1): Added an option to omit the callback_url parameter, as this removes the back button on the dLocal payment page.
• Stripe (STRV2-EP1-CC): 3DS result data from Stripe is now included in callbacks.
• Worldpay (WOR-EP1): Added a new setting, Debit waits for webhook, to postpone marking a debit transaction as successful. This setting waits for the capture event webhook notification instead of relying solely on the authorization webhook.

Added​

• Worldline (ING-EP2-MUB): Added support for the Multibanco payment method (bank transfer). Multibanco is the largest interbank network in Portugal.

Fixed​

• Adyen (ADY-EP3): Updated the API documentation to include the merchantOrderReference parameter.
• Braintree (BRA): Added support for settling chargeback reversals.
• DPO Pay (PAYGA-PYGT-CC): Updated the adapter documentation to cover new capabilities (PreAuth, Void, Capture).
• E-Comprocessing, eMerchantPay (ECP-EP1, EME-EP3-CC): Added API documentation for eMerchantPay and E-Comprocessing.
• MultiSafepay (MUL-EP1): Fixed a typo in the status used by callback handling for chargebacks.
• Nuvei (NUV-EP1): Updated the API documentation to include information on mandatory fields.
• Nuvei (NUV-EP1-CC): Fixed an issue that caused the transaction ID to be incorrectly set to IXOPAY's internal UUID until the callback is received.

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.