6 posts tagged with "Dashboard"

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

API​

Added​

• Push API: Add transactionSubType to the /chargeback endpoint.

Features​

Changed​

• Risk Profile: Add parameters to Count Chargebacks Risk Engine Strategy to include or exclude RDR transactions.

Added​

• Account Updater: Add connector setting Account Updater: Snooze Updates for Status Contact-Cardholder to skip future account updater runs for the response status Contact-Cardholder for up to 36 months.
• BI Data Source: Add field subType to the BI Data Source enabling better transaction distinction and filtering of RDR transactions.
• Dashboard: Add a filter for subType to Trend: Compare Chargeback Rate dashboard widget.
• Post Processing Jobs: Add Transaction Type and Transaction Subtype columns to the exported email of the Send Reports to Merchants post-processing job strategy.
• Risk Profile: Add Is Credit Card Prepaid and Is Credit Card Reloadable risk rules.
• Transaction List: Add field subType to the Advanced Filter enabling better transaction distinction and filtering of RDR transactions.

Fixed​

• Transaction Details: Fix Load More button for transaction logs exceeding 100 entries.

Adapters​

Changed​

• Bangkok Bank (BB): Add optional PGPPrivateKey and PGPKeyPassPhrase fields to the data fetcher's Extra Data, to support PGP-encrypted settlement file decryption.
• checkout.com (CHE): Remove the requirement to send customer.bic or customer.extraData.bic fields and the requirement to perform a separate /options getIssuers call.
• CMI (CMI): Add support for settlement handling.
• Nuvei (NUV-EP1): Remove the requirement to send customer.email, this is now an optional field.
• PayTabs (PAYT-EP01): Add connector config Enable iframe mode to support checkout via iFrame.
• PPRO (PPR-EP1): Add a configuration option for alternative PPRO return mode.
• Worldpay (WOR-EP1): Add support for chargeback notifications.

Added​

• Fiuu (FIUU-EP1): Add the Fiuu (formerly Razer Merchant Services) adapter with support for debit and refund transactions. Fiuu is Southeast Asia's leading payment gateway, enabling seamless payments for businesses and individuals.
• JPMorganChase (CHA-EP2): Add the J.P.Morgan Commerce Platform adapter with support for debit, preauthorize, (partial) capture, (partial) refund, and recurring transactions. J.P. Morgan is a leader in financial services, offering solutions to clients in more than 100 countries with one of the most comprehensive global product platforms available.

Fixed​

• KakaoPay (KAKAO-EP1): Add extraData.paymentMethodType field with possible values MONEY or CARD.
• KCP Mobile, KCP PC (KCPMO-EP1, KCPPC-EP01): Fix live endpoint.
• PayPal Complete Payments - PPCP (PPCP-EP1):
  • Fix missing prepareCallEndpoint for the multi-method payment connector.
  • Ensure PPCP payment method availability in the multi-method payment connector.
• SIA (SIA-E01): Fix setting transaction status to error on failed 3DS authentication, enabling follow-up THREEDSAUTHORIZATION2 call.

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.