Skip to main content

7 posts tagged with "Dashboard"

View All Tags

Gateway β€” v26.16

Gateway Features​

Changed​

  • Data Export: Merge split payment data into the transaction's own row instead of writing a separate row per split.
  • Transaction List: Show split payment details within the transaction's own row instead of separate rows.

Added​

  • BI Data Source: Add the scheme lifecycle identifier and reference scheme lifecycle identifier as searchable fields in the Advanced Search.
  • Risk Profile: Add Riskified's fraud decision result to the callback notification and transaction API response.

Fixed​

  • 3-D Secure: Fix an issue where soft-decline 3-D Secure is not properly handled.
  • Callback: Fix an issue where the chargeback amount in the callback notification was sent as a number instead of a string.
  • Dashboard: Fix an issue where dashboard pivot table reports could return incomplete results.
  • Hosted Payment Pages: Fix an issue where Content Security Policy headers could be added to Hosted Payment Pages responses for tenants that had not configured a policy.
  • Provider Settlements and Reconciliation: Fix an issue where settlement amount calculations could use an imprecise exchange rate.
  • Risk Profile: Fix an issue where item and browser data could be missing or incorrect in Riskified risk checks.
  • Transaction List: Fix an issue where searching by Additional ID 1 or Additional ID 2 did not return matching transactions in the transaction list.

Gateway Adapters​

Changed​

  • 2C2P (2C2P): Add an option to map the commission VAT amount as a dedicated commission-VAT fee instead of a scheme fee.
  • checkout.com (CHE-EP2-CC): Add the Account Name Inquiry result to the callback notification for register transactions when enabled via the accountNameInquiryEnabled configuration.
  • Dimoco (DIM): Add support for chargeback reversals.
  • Klarna (KLW): Add a new data fetcher setting addNetSettlementAmountLineItem to enable actual-net-settlement-amount for settlements.
  • Paynetics (PNE): Add support for CHB2 chargeback and reversal reconciliation, including RDR sub-type mapping.
  • Stripe (STRV2-EP4-KBNPL): Add support for the new payment method Klarna. Klarna is a Swedish payment provider allowing customers to pay via invoice, direct debit, or installment-based financing at checkout.
  • Worldpay (WOR-EP1-CC): Add support for the Mastercard Transaction Lifecycle Identifier (TLID) mandate for stored-credential transactions.

Added​

  • du Pay (DUP): The du Pay push adapter allows cash deposits made at du Pay kiosks to be pushed to the IXOPAY platform, ensuring that these transactions are also available within the system.

Fixed​

  • Dimoco (DIM): Fix an issue where chargeback settlements could be created from the wrong record.
  • Stripe (STRV2): Fix an issue where StripeConnect platform credentials could fail to load.

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 β€” 26.13

Gateway Features​

Changed​

  • Post Processing Jobs: Add a credit card token type filter to Batch Less: Aggregate Transaction Values To Job Line Items strategy.
  • Provisioning API: Add Network Token TRIDs to the listMerchants response.

Added​

  • Hosted Payment Pages: Add possibility to manage and configure Content Security Policy (CSP) headers.
  • Provider Settlement: Add automatic detection of second chargebacks when the first chargeback was already settled.
  • Provisioning API: Add a new dedicated endpoint to configure and retrieve the multi-method routing configuration.

Fixed​

  • Dashboard: Fix an issue where dropdowns in the dashboard did not work in Safari.
  • Network Tokenization: Fix an issue where tokens stored during cross-merchant transactions with register were not marked active.
  • Post processing: Fix the CAMT.053 settlement export to skip files with no reportable entries and to use fallback values for currency, account name, and booking date.
  • Post processing: Fix the settlement net amount shown when the fee currency differs from the settlement currency.
  • Provisioning API: Fix error responses to always return a consistent JSON format.

Gateway Adapters​

Changed​

  • 2C2P (2C2P-EP1-CUP): Add UnionPay support as a dedicated UPOP payment method.
  • 2C2P (2C2P-EP1-MACAU): Add support for the new payment method Macau Pass. Macau Pass is a widely used stored-value card and mobile payment service in Macau; customers complete the payment on a hosted page, with MOP as the supported currency.
  • Adyen (ADY): Add support for handling chargebacks.
  • Autopay (AUTO-EP1): Add handling of the scheme transaction identifier in callback notifications, storing it as the transaction's scheme reference.
  • dLocal (DLO-EP1-CC): Add support for installments.
  • EBANX (EBA): Improve callback notification and error handling for the Pix, Pix Automatico, and UPI payment methods with consistent status and error mapping.
  • EBANX (EBA-EP1-PIX): Add support for the new payment method Pix. Pix is Brazil's instant payment system operated by the Central Bank of Brazil, allowing customers to pay in real time via QR code.
  • NaverPay (NAV): Improve error mapping for failed transactions.
  • Paynetics (PNE):
    • Add parsing of TRN2 transaction reports for reconciliation when the new report retrieval mode is enabled, replacing the legacy POF-based reconciliation.
    • Add support for chargeback handling.
  • PayU (PAU): Add support for sending a merchant-provided tax amount with payment requests via a new configuration setting.

Fixed​

  • Adyen (ADY): Fix callback handling for incremental authorizations.
  • Adyen (ADY-EP2-SEP): Fixed an issue where recurring transaction were failing.
  • EBANX (EBA-EP1): Fixed an issue where the adapter log captured the first partial refund ID instead of the current partial refund ID.

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 β€” v26.8

Gateway Features​

Added​

  • User Management: Add read-only access to Global Routing Profiles and Connector Aliases, allowing users to view configurations without the ability to make changes.

Fixed​

  • Dashboard: Fix an issue where the date range filter calendar in the dashboard was not responding.
  • Network Tokens: Fix an issue where customer profiles did not process with network tokens.
  • Provider Settlements and Reconciliation: Fix an issue where amounts in settlement export reports for CAMT.053 files could be negative.
  • Transaction Processing: Fix payout responses to include merchant advice codes in the transaction result.

Gateway Adapters​

Changed​

  • checkout.com (CHE-EP1-CC,CHE-EP2-CC):
    • Add documentation for the extraData.digitalGoods:type parameter for Account Funding Transfer transactions.
    • Add support for partial authorization, including the authorized amount and status, in transaction responses and callback notifications.
    • Add the network decline code and merchant advice codes to transaction responses and callback notifications.
  • Dimoco (DIM): Adjustments to commission and scheme fee handling.
  • dLocal (DLO-EP1-PUNTO): Add support for payments in Nicaragua via the PuntoXpress payment method.
  • eMerchantPay (EME-EP2-SEP): Include the mandate reference in the callback notification for recurring direct debit transactions.
  • JPMorganChase (CHA): Add a new dedicated line item to aggregate fees for disputes.

Fixed​

  • Dimoco (DIM): Fix an issue where settlement files are incorrectly imported multiple times.
  • Nuvei (NUV-EP1-CC): Fix an issue when using customer profile tokens for subsequent transactions.
  • PayPal Complete Payments - PPCP (PPCP-EP1-CC): Fix an issue where the payment instrument was not properly registered through the hosted payment page using customer profiles.
  • PayU (PAU): Fix an issue where settlement files containing dates in an alternative format were not parsed correctly.

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 β€” v25.10

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.

Gateway, Portal β€” v25.6

Gateway API​

Fixed​

  • Transaction Processing: Fixes the validation for follow-up transactions to consider failover transactions.

Gateway Features​

Fixed​

  • Dashboard: Fixes an edge case where a successful manual refund results in an error page.
  • Risk Profile: Improves the handling of invalid configurations for the Credit card PAN Check risk check.
  • Transaction List: Fixes the functionality of the delete button in the advanced search filter.

Gateway Adapters​

Changed​

  • Stripe (STRV2): A new option is made available in the Descriptor configuration to utilize the value provided in extraData.statement_descriptor.
  • Worldpay (WOR-EP1): Add support for the new payment method Klarna. Klarna is a service pioneered by Swedish innovators that redefines the online shopping experience by offering flexible payment options. It provides consumers with versatile and convenient ways to pay, making shopping more adaptable to individual needs.

Added​

  • Adyen (ADY-EP4-CC): Add the Adyen POS adapter with added support for processing transactions using Point of Sale terminals. Adyen is a global payment service provider and technology platform that empowers businesses with secure and versatile payment solutions.

Portal​

Added​

  • Proxy Tokenization Page:
    • Add Proxy filter. This allows you to filter results for a specific proxy profile
      • Explicit identifier of proxy filter
      • Filter is always present
      • Returns matching vault and filters non matched proxy profiles
        • Profile Name
        • Profile Description
        • Profile URL
        • Profile ID
        • Profile Alias
    • Brand Vault filter. This provides clarification to what values can be filtered
      • Explicit identifier of proxy filter
      • Filter is always present
    • Delete Proxy Profile. This enables users to delete proxy profiles
      • Removes proxy
    • Create Proxy Alias. This enables users to create proxy alias without a support ticket
      • Adds new Alias.

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.