Skip to main content

9 posts tagged with "Risk Profile"

View All Tags

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.

Gateway — v25.0

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.

Gateway — v24.21

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.

Gateway — v24.13

API​

Changed​

Fixed​

  • Pay-by-Link API: Fixed an issue that would prevent a pay-by-link transaction from being canceled if a failover occurred for the transaction.
  • Push API: Fixed an issue that would cause a type error if an empty body request was submitted in a Push API request.
  • Transaction API: Fixed an issue where invalid 3DS values (browserColorDepth, browserTimezone) sent to the API in transaction data would cause an error. These invalid values are now ignored.

Features​

Changed​

  • Connector Settings: The "Postback: Include 3DS Data" connector setting is now also available in the global settings.
  • Post Processing Jobs: Optimized the process of collecting transactions in post-processing jobs.
  • UI Navigation: Improved the parent tenant selection when creating a new tenant. By default, the current tenant is set as the parent tenant and the drop-down is now searchable.
  • UI Navigation: Updated risk logs so that they are loaded asynchronously. This improves the initial load time for the transaction details view. Risk data is now only loaded when expanding the view.

Added​

  • Connector Configuration: Added audit logs for the "Additional Configs" in the connector view.

Fixed​

  • Audit Log: Fixed an issue that would cause an error when accessing the audit log if the corresponding merchant cannot be found when checking access permissions.
  • Fee Management: Fixed an issue that would cause an error when changing the mapping to a different fee entity. The mapping for the old fee entity is now removed, and the mapping is set to the new fee entity.
  • Post Processing Setting: Fixed an issue with the "Create unknown transaction on connector with GUID" option for settlements that prevented unknown transactions in a settlement file from being added to the platform.
  • Provider: Fixed an issue that would occur when saving a connector configuration. Previously configured connectors that were assigned to the same provider were removed when the configuration was saved, with only the new configuration linked to the provider.
  • Provider Settlements and Reconciliation: Fixed an issue that would cause an error when trying to sort missing reconciliation data by merchant.
  • Risk Profile: Fixed an issue where saving a risk rule without entering parameter values would result in a type error.
  • Risk Profile: Fixed an issue that would cause an error when opening risk rules if the risk rule set ID referenced a risk rule set that does not exist. A 404 error is now displayed instead.
  • Transaction Processing: Fixed an issue caused by the platform attempting to collect 3DS information for Apple Pay transactions. The system now checks whether a transaction uses Apple Pay before collecting additional 3DS information.
  • UI Navigation: The loading page displayed for the collectMissing3DSecureData connector configuration was only displayed in English. The page is now displayed in the language of the transaction where available, with English as the fallback language.

Adapters​

Changed​

  • American Express (AMX-EP1-AMX): Added a new gateway connector configuration option, "Force System Generated STAN". This option can be used to force the system trace audit number (stan) to be generated by the IXOPAY platform and stored in the additionalId1 field. The following options are available to determine the format of the STAN:
    • "Yes - Uppercase characters only"
    • "Yes - Upper- and lowercase characters".
  • Banca Intesa (BAI-EP1): If the PSP includes the TRACEID in a transaction response, it is now included in the postback.
  • Braintree (BRA-EP1-BLI): Added support for partial refunds for the Blik non-redirect payment method.
  • Braintree (BRA-EP1-PPE): Added support for line items and a corresponding option, includeLineItems has been added to the connector configuration.
  • dLocal (DLO-EP1-CC): The merchantTransactionId is now passed to the vault, in order to pass it on to the PSP in refund requests.
  • HypYaad (HYP): Removed the mapping of payment references in settlement files, as this could lead to a single settlement file being split into multiple settlements.
  • Mastercard Payment Gateway Services (MPG, BAMI): Added support for the scheme transaction ID.
  • Nexi Group (NETS-EP1): Added support for specifying the language in the checkout payload for transactions. This ensures that the language field is included in the payload if it is included in the transaction's extra data.
  • PayPal (PPA-EP1-PPE): Added the isFinalCapture flag for capture transactions. If set to true, the capture is marked as final on the PayPal side and no further captures are possible.
  • Simulator: Added support for incremental authorization for simulated credit card transactions.

Added​

  • WavePay (WAV): The WavePay push adapter allows cash collection payments to be pushed to the IXOPAY platform to ensure that these transactions are also available within the system.

Fixed​

  • Afterpay (AFT): Fixed an issue with retrieving the minimum/maximum price, caused by a missing interface.
  • American Express (AMX-EP1-AMX): Fixed an issue that would cause an error if settlement files are not formatted correctly.
  • Braintree (BRA): If rows in a settlement file did not include a settlement date, the settlement date was previously taken from the first value found in the "Settlement Date" column of the file. However, this could result in the settlement date being incorrect. The behavior has therefore been changed to set the settlement date to the transaction's disbursement date instead.
  • Braintree (BRA-EP1-PPE): The merchantAccountId is now only passed to Braintree's JavaScript SDK if a value is present.
  • iyzico (IYZ):
    • Fixed an issue with that would cause the batch number to be set to the entire file name of the settlement file, rather than the initial numerical portion of the file name. This was caused by empty rows in the settlement file.
    • Fixed an issue that would cause some settlement files to be parsed incorrectly.
  • Khipu (KHI): Fixed an issue with retrieving the bank list, caused by a missing interface.
  • Klarna (KLW): Fixed an issue that would result in the error "Invalid Response" being returned for transaction without a body. An empty body is now handled correctly, with the HTTP error code being checked prior to parsing the response.
  • Mashreq (MASH-EP01): Fixed an issue where the status of successful transactions was not set correctly due to the status in the response not being formatted as expected.
  • Payabl (P21): Fixed an issue caused by the error code parameter being evaluated incorrectly.
  • Paymee (PAYME-EP1-CCRD): Fixed an issue where refund amounts would be sent with a varying number of decimal places, which could sometimes lead to errors. Refund amounts are now formatted consistently.
  • Trustly (TRU): Fixed an issue that would cause a generic payment error if the private key required to generate the signature was missing. The system now checks for its presence.

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.