11 posts tagged with "dLocal"

Gateway API​

Added​

• Transaction API: Add the includeTracing parameter for Status API and Transaction API for debit & preauthorize requests, enabling transaction routing and cascading details in the Status API response and Transaction API callbacks.

Gateway Features​

Changed​

• Audit Log: Update the User-Management report to reflect the selected user type (userType), include user descriptions (description), the merchant column (merchant) for relevant user types.

Added​

• Connector Settings: Add a new connector setting: Expire transaction with a given status after given minutes, allowing configuration of multiple statuses and expiration times. This replaces the need for separate settings for pending and automatic transaction expirations.
• Transaction Details:
  • Allow adding custom data values to manual refunds and captures, configurable in tenant settings.
  • Introduce a new permission, frontend.transaction.add-extradata-to-manual-capture-refund, to manage access to this feature.
• Transaction List: Restore the Copy from Standard Filter button in the advanced search.
• User Management: Add a new field, Description, to the base data for all users, visible in the Create New User, Edit User, and User Overview views.

Removed​

• Connector Settings: Deprecate the connector settings Expires pending transactions after given minutes and Transactions: Expire automatically after (x) minutes, as their functionality is now covered by the new setting that supports expiring transactions based on specific statuses.

Gateway Adapters​

Changed​

• EquensWorldline (EQW): Add ARN (Acquirer Reference Number) to settlement when parsing reconciliations.
• JPMorganChase (CHA-EP2-CC): Improve documentation for new extraData fields (extraData["card.cardVerificationResult"], extraData["card.cardVerificationResultCode"], and extraData["card.paymentAccountReference"]).

Fixed​

• dLocal (DLO-EP1): Correct the payout country restrictions link in the adapter documentation.

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.

Gateway API​

Fixed​

• Provisioning API: Fix an error that occurred when attempting to update merchant users with apiUserSettings configured.

Gateway Features​

Changed​

• Connector Configuration: Change save message of connector configuration to display multiple validation errors simultaneously, instead of just one.
• Risk Profile:
  • Applied cosmetic changes for consistency, including button renaming and layout adjustments.
  • Restricted Audit Log access with the Admin User Permission misc.show-public-audit-log.

Added​

• API Testing: Add a Clear CC Token button to the API Testing view to reset credit card fields without refreshing the page.
• Risk Profile: Add a new risk rule to validate the presence of both the transaction indicator and reference scheme ID.
• Risk Profile: Add support for BIN segments (Consumer, Business, Commercial, Government, Unknown) and add a new risk rule BIN segment of credit card is [in, not in] [list of segments] to replace the previous BIN level of credit card is [in, not in] [list of levels] rule in the future, allowing checks for specific BIN segments.

Fixed​

• Connector Settings: Fix compatibility of the Manipulation: Always set withRegister connector setting on meta-connectors with Customer Profiles to ensure payment instruments are properly stored.
• Provider Settlements and Reconciliation: Fix an issue where the upload button remained in the uploading state after a manual file upload error.

Gateway Adapters​

Changed​

• dLocal (DLO-EP1):
  • Add /options/installmentsPlan endpoint to retrieve installment plans.
  • Add extra data parameters to debit and preauthorize transactions to enable installements (extraData.installments and extraData.installments_plan_id).
  • Change required status of customer.nationalId from mandatory to optional.
• JPMorganChase (CHA-EP2): Add support for partial void transactions.
• KakaoPay (KAKAO-EP1): Add support for settlement and reconciliation handling.
• Nuvei (NUV-EP1):
  • Change required status of customer.email from mandatory to optional.
  • Change sFTP retrieval to no longer require permissions to rename the file on the remote server for settlement and reconciliation handling.
• PayPal Complete Payments - PPCP (PPCP-EP1): Add chargeback protection details to postback response, including seller protection status (extraData.seller_protection_status), dispute categories (extraData.seller_protection_dispute_categories), and PayPal account status (extraData.paypal_account_status).
• Worldpay (WOR-EP1): Add postback handling for online refunds. Merchants will receive the Refund Authorisation Reference number in extraData.refundAuthorisationReference via postback.

Added​

• Banco Popular Dominicano (BPD-EP1): Add the Banco Popular Dominicano adapter with support for debit transactions. Banco Popular Dominicano is the first privately owned bank in the Dominican Republic and is the leader in a wide range of banking and financial services in the country. It is the principal company of Grupo Popular.

Fixed​

• Global Payments (GBP): Prevent duplicate settlement errors by using more specific settlement batch numbers.
• JPMorganChase (CHA-EP2):
  • Fix handling of partial void followed by capture.
  • Update extraData.totalAuthAmount after partial void.
• PayPal Complete Payments - PPCP (PPCP-EP1-PPE):
  • Enable partial capture and void capabilities for the PayPal payment method via the PayPalCompletePlatform adapter.
  • Ensure that the PayPal Partner Attribution ID is set for transactions processed through multi-method connectors.
• PXP (PXP-EP1): Fix mapping of error code 100(77).
• Stripe (STRV2-EP1): Use net amount instead of gross amount when parsing Line Items and Rolling Reserve for the Stripe Settlement Report.

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​

• Transaction API: Fix an issue where invalid browserScreenHeight or browserScreenWidth values caused errors. Now, any invalid values are properly handled to ensure smooth processing.

Features​

Changed​

• Transaction Processing: Remove the billing country restriction for the iDeal payment method, allowing values beyond NL and BE.

Added​

• Hosted Payment Pages: Add data attributes to the Google Pay button for easier configuration on the Hosted Payment Page (HPP). Supported attributes include data-button-color, data-button-type, data-button-radius, data-button-size-mode, and data-button-locale.

Fixed​

• Customer Profiles:
  • Fix an issue where the action buttons for Payment Instruments in the Customer Profile merchant view were not displayed.
  • Fix a bug where deregistering via the action button in the Customer Profile merchant view did not work properly.
  • Fix a bug where the detach and deregister actions for Payment Instruments in the Customer Profile merchant view did not reset the preferred payment method.
• Pay-by-Link: Fix an issue where Pay-by-Link (PBL) data failed to display when customer information was missing from the transaction; it will now display correctly even if customer data is absent.
• Provider Settlements: Fix an issue when settling preauthorize and void transaction fees.
• Provider Settlements and Reconciliation: Fix an issue in settlement processing where refunds referencing pre-authorized transactions were not correctly matched to their capture transactions.
• Transaction Processing: Fix surcharge calculation for direct PCI API requests.

Adapters​

Changed​

• HUA NAN COMMERCIAL BANK (HNCB-EP2-HBQR): Update the encryption process for the HNCB QR payment method to use the PSP’s encryption endpoint instead of local encryption.
• Volt (VOL-EP1):
  • Add pay-by-link capability.
  • Add JWT signature support for refunds to ensure strong customer authentication (SCA) compliance.

Fixed​

• dLocal (DLO): Fix issue with postback handling by using the correct transaction ID from the currently processing refund transaction, instead of the order ID from the debit.
• PXP (PXP-EP1-CC): Fix the handling of transactionSubType in PSP callbacks to ensure proper support for Rapid Dispute Resolution (RDR).

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​

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