11 posts tagged with "Risk Profile"

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

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.