7 posts tagged with "Dimoco" | Page 2 of 2

Gateway Features​

Added​

• payment.js: Add support for ARIA attritbutes for card number and security fields.
• Post Processing Jobs: Display seller names in Transaction Reports for split payments.

Fixed​

• Multi-method connector: Fix failover transactions with customer profiles.

Gateway Adapters​

Changed​

• Adyen (ADY-EP3-MOPAY): Add support for the new payment method MobilePay. MobilePay is a popular digital wallet in Denmark and Finland, enabling customers to pay securely via a mobile app linked to their payment card or bank account.
• Autopay (AUTO-EP1): Add support for Customer-Initiated Transactions (CIT) and Merchant-Initiated Transactions (MIT).
• dLocal (DLO-EP1-AOZ): Add support for the new payment method Virtual Accounts Japan. This payment method facilitates bank transfers using either Dynamic Virtual Accounts (unique per transaction) or Static Virtual Accounts (assigned per merchant/customer), enabling automated and accurate reconciliation for Japanese payments.
• dLocal (DLO-EP1-BRE): Add support for the new payment method Bre-B. Bre-B is Colombia's national instant payment system, allowing customers to pay directly from their participating bank app or digital wallet by scanning an interoperable QR code.
• dLocal (DLO-EP1-CAPI): Add support for the new payment method Capitec Pay. Capitec Pay is a South African payment solution that enables customers to pay securely and directly from their bank account by authenticating the transaction via the Capitec banking app.
• dLocal (DLO-EP1-QRARG): Add support for the new payment method QR Interoperable Argentina. QR Interoperable is a solution based on the Transferencias 3.0 initiative, enabling customers to pay by scanning a single, standardized QR code using any compatible banking app or digital wallet in Argentina.
• dLocal (DLO-EP1-QRIS): Add support for the new payment method QRIS. QRIS (Quick Response Code Indonesian Standard) is a unified QR payment system regulated by Bank Indonesia, allowing customers to pay using any supported e-wallet or banking app by scanning a single code.
• dLocal (DLO-EP1-THAI): Add support for the new payment method Thai QR Payment. Thai QR Payment is Thailand’s national QR standard, enabling instant, cashless payments by scanning a code from any compatible mobile banking application.
• dLocal (DLO-EP1-VAIND): Add support for the new payment method Virtual Accounts Indonesia. This digital payment method assigns a unique virtual account number to each customer, allowing them to complete transactions via bank transfer using their preferred Indonesian banking app or ATM.
• dLocal (DLO-EP1-VNP): Add support for the new payment method VNPay-QR. VNPay-QR is a widely used payment solution in Vietnam, allowing customers to pay securely by scanning a QR code directly from supported mobile banking apps and e-wallets.
• GoCardless (GOC): Update documentation.
• GoCardless (GOC-EP1-BTR): Improve error mapping.

Added​

• JPMorganChase (CHA): Fix settlement validation logic to correctly handle optional fields based on the transaction type.

Fixed​

• Bangkok Bank (BB):
  • Fix parsing of negative refund amounts in settlement files.
  • Fix mapping of the net settlement amount to use the net payout value instead of the gross amount.
• Dimoco (DIM): Add support for processing TK011 and TK012 settlement files.

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​

• Customer Profiles: Add a new flag for the payment selection page to allow storing a payment instrument without automatically linking it to the customer profile.
• Hosted Payment Pages: Add support for the setRequireCardHolder method in PaymentFormV2.
• Job Configuration: Add a new filter Transaction Types to the Collect Transactions by Uploaded CSV File strategy to collect only transactions of the selected types. Not selecting any types will apply no filter.
• Provider Settlements and Reconciliation: Add a new constraint to specify whether transactions are from a merchant of type marketplace.

Fixed​

• Job Configuration: Fix the Collect Transactions by Uploaded CSV File strategy to ignore invalid uploaded files.

Gateway Adapters​

Changed​

• Adyen (ADY-EP3-P24): Add support for the Online Banking Poland payment method. This real-time bank transfer option allows customers to securely pay directly from their bank account and is widely used in Poland for e-commerce transactions.
• checkout.com (CHE-EP1-CC): Add a configuration to enable Account Name Inquiry (ANI) for register transactions.
• Dimoco (DIM): Add a new configuration option to select between the old and new Settlement and Reconciliation retrieval logic. By default, the old logic is used.
• dLocal (DLO-EP1-UPI): Add support for the UPI (Unified Payments Interface) payment method. UPI is an instant real-time payment system widely used in India, enabling customers to transfer funds directly between bank accounts via mobile or web applications.
• JPMorganChase (CHA-EP1-CC): Add support for retrieving and processing a new settlement report entity type Funded Transaction Fee Details (FTI).
• Klarna (KLW): Add a new fee type representing the total VAT amount for settlements.
• PayPal Complete Payments - PPCP (PPCP): Add a new setting to include customer billing and shipping details from PayPal in the callback request.

Fixed​

• DigitSecure (DS-EP1-T2P): Resolve an issue where the Transaction Details page could not be loaded.
• Nuvei (NUV-EP1): Fix a bug where the wrong identifier was stored as the adapter transaction ID.
• Stripe (STRV2-EP1): Fix an issue that prevented configuring reconciliation handling.
• Stripe (STRV2-EP3): Fix an issue that prevented configuring reconciliation handling.
• Worldline (ING-EP8-CC): Fix minor payload change for captures.

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.