17 posts tagged with "dLocal"

Gateway Features​

Changed​

• Provider Settlements and Reconciliation: Rename Reconciliation Conflicts page to Provider Reconciliations.
• Risk Profile: Rename Cumulative Score column to Total Score.

Added​

• Connector Settings: Add a new connector setting Postback: Defer sending until after the API response has been returned.

Fixed​

• Transaction Processing: Fix an issue that could cause a Token not found error in certain circumstances.

Gateway Adapters​

Changed​

• dLocal (DLO-EP1-MP): Add support for the new payment method MultiPago. MultiPago is a cash-based payment method in Latin America that allows customers to pay for online purchases using payment slips at convenience stores or banks.
• Nuvei (NUV-EP1-ALIUN): Add support for the new payment method Alipay+ Unified Payment. Alipay+ Unified Payment is a cross-border digital payment solution that allows customers to pay with various supported e-wallets and other payment methods across multiple regions.
• Nuvei (NUV-EP1-RAKUT): Add support for RakutenPay, a Japanese e-wallet that lets customers pay online or in-store via the app or by scanning a QR code.
• PayPal Complete Payments - PPCP (PPCP): Add support for sending transaction context if data is provided.
• PayPal Complete Payments - PPCP (PPCP-EP1-PPE): Add a new setting useProvidedMerchantUrls to fix mobile payment processing for merchants using PayPal's iOS/Android SDK.

Fixed​

• Cybersource (CYS-EP1-CC): Fix mapping of transaction indicators to the commerceIndicator.
• JCC Payment Systems (JCC-EP1-CC): Fix mapping and handling of callback notifications.
• KakaoPay (KAKAO-EP1-KAKAO): Fix refund handling to ensure each refund is correctly matched and settled.
• Worldpay (WOR): Ensure correct behavior for debit transactions by setting delay capture to 0.

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 bug where an auto-generated shared secret on connector creation returned a value longer than the actual stored one.

Gateway Features​

Changed​

• Risk Profile: Update Forter risk engine to use Dispute API (v10.1).
• Risk Profile: Add configurable Forter risk engine 3DS recommendations with an option to adjust 3DS requirements for transactions based on those recommendations.

Added​

• Fee Management: Add new fee constraint 3DS (options: any or inhouse) which allows setting fees based on the 3DS environment used for a transaction.
• Fee Management: Improve the transactionSubType constraint by showing any as the default option.
• Transaction Details: Add viewing of fraud tags in the Transaction Details page for merchant users. Enable with the frontend.transaction.tag.show permission. Admin users have the transaction.tag.show permission enabled by default.
• Transaction List: Add the Advanced Filter with a simplified set of filter options for merchant users in the Transactions view. It can be enabled with the frontend.transaction.advanced-search permission.

Fixed​

• Risk Profile: Fix an edge case where transaction risk data couldn't be stored.

Gateway Adapters​

Changed​

• dLocal (DLO-EP1-VPAY): Enable V Pay for Paraguay.
• JPMorganChase (CHA):
  • Add new setting to select report type: Funded Transaction Fee Details (FTI) or Settlement Details (PE).
  • Add new setting to specify settlement retrieval type: Polling-Based Retrieval or Notification-Based Retrieval.
• Nuvei (NUV-EP1-PSE): Update documentation for payment method PSE.

Fixed​

• JPMorganChase (CHA): Fix several issues with notification handling and settlement file retrieval.
• MultiSafepay (MUL-EP1-CC): Attempt to retrieve the scheme reference identifier from the initial MultiSafePay transaction if it was missing in order to facilitate recurring transactions.

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

Changed​

• Audit Log: Improve audit logs sorting.
• Risk Profile: Resolve edge-case race condition causing incorrect risk check data calculation.
• Risk Profile: Update Forter risk engine to use Orders API V3 (v10.1) and Order Status API V2 (v10.1).

Added​

• Post Processing Jobs: Add new job settings page to manage job status, steps, and conflict states. A new permission, postprocessing.job.update-settings, has been added to enable this.

Gateway Adapters​

Changed​

• ACI PAYON (PON-EP1-CC): Update provider 3-D Secure flow to support method fingerprinting.
• Adyen (ADY):
  • Add new data fetcher setting to map Tax Charge to either Service Fee or VAT.
  • Store Auth Code and Scheme Transaction Identifier from postbacks for reuse in subsequent transactions.
• Adyen (ADY-EP3-VIPPS): Enable partial capture for the Vipps payment method.
• PayU (PAU-E01-PAE): Add support for the new payment method PagoEfectivo. PagoEfectivo is a Peruvian cash-based online payment service that lets customers generate a payment voucher and settle it in cash at participating banks or retail locations.
• PayU (PAU-E01-YAPE): Add support for the new payment method Yape. Yape is a Peruvian mobile wallet that lets customers pay merchants or transfer money using their phone number or by scanning a QR code.
• Simulator: Tweak simulated 3-D Secure challenge page.

Fixed​

• dLocal (DLO): Fix settlement handling to correct amount formatting, ensure fees are deducted from the payout sum, and store fees to their respective transactions.
• PayPal (PPA): Prevent duplicate fees when receiving multiple callbacks for the same transaction.
• PXP (PXP): Fix status mapping of state 13 (AuthorisedByProvider) to a successful transaction.

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

Added​

• Provider Settlements and Reconciliation: Add ability to manually upload reconciliation files.

Fixed​

• Post Processing Setting: Fix a bug where setting a provider's adapter to - caused an error.
• Transaction Processing: Improve handling of follow-up transactions to prevent errors after deregistration.

Gateway Adapters​

Changed​

• Adyen (ADY): Improve error mapping to consider the reason value when provided.
• Adyen (ADY-EP4): Add documentation for referenced and unreferenced Refunds.
• Certegy (CERTE-EP1-ACH): Fix Register and Refund handling.
• DPO Pay (PAYGA-PYGT): Add support for Partial Refunds.
• PPRO (PPR-EP1): Update the endpoint from https://api.girogate.de to https://simpleapi.ppro.com.

Fixed​

• Adyen (ADY-EP3): Fix an issue where extra data was not forwarded for Refunds.
• Bangkok Bank (BB): Fix handling of negative VAT values for settlements.
• dLocal (DLO): Fix an issue with parsing settlement files.

iFrame​

Added​

• UT iFrame: Export TypeScript types from main entry point for standard importsConfiguration, Authentication, HMACAuthentication, and other key types now available. Resolves issue requiring non-standard import paths from node_modules.

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​

• BI Data Source API: Fix wrong HTTP response header for the BI Data Source API. The response header now returns a proper Content-type: application/json; charset=UTF-8 header.

Gateway Features​

Changed​

• Connector settings: Rename the Pay By Link tab in connector settings to Templates. This tab now consolidates email template configurations, including those for Pay By Link and the new general transaction success confirmations.

Added​

• Connector settings: Enhance transaction confirmation emails: You can now enable automated emails for merchants and/or customers upon any successful transaction, extending beyond Pay By Link. Control this using the new settings Send Success Mail to customer and Send Success Mail to merchant, located in the Templates tab (availability of this feature is subject to user permissions).

Fixed​

• Dashboard: Fix dashboard visualization issue when no time range is provided.
• Risk Profile: Fix a column sorting issue for the representment table.

Gateway Adapters​

Changed​

• Cybersource (CYS-EP1): Add option to provide a reconciliation ID via extra data.
• DPO Pay (PAYGA-PYGT): Add status retrieval to determine actual status of failed transactions.
• Redsys (RED-EP2): Add mapping for the Auth-Code when available.

Fixed​

• Adyen (ADY-EP3-PAYPA): Fix postback handling issue.
• dLocal (DLO): Add handling for missing customer data.

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.