Manual Chapter : Configuring a URL for receiving automatic transactions data

Applies To:

Show Versions Show Versions
Manual Chapter

Configuring a URL for receiving automatic transactions data

You need to configure a separate URL for receiving automatic transactions data only if the form action in the HTTP request from the client does not refer to the URL from which the request is being sent.
You configure a receiving URL for automatic transactions to ensure that your server can process automatic transactions data.
  1. On the Main tab, click
    Security
    Fraud Protection Service
    Anti-Fraud Profiles
    .
    The Anti-Fraud Profiles screen opens.
  2. From the list of profiles, select the relevant profile.
    The Anti-Fraud Profile Properties screen opens.
  3. In the Anti-Fraud Configuration area, click
    URL List
    .
    The URL List opens.
  4. Select the check box next to the URL where the client sends data that is configured for Automatic Transactions detection.
  5. Click the
    Clone
    button.
    The Clone URL pop-up screen opens.
  6. In the
    URL Path
    field, type the URL that is referred to in the form action of the HTTP request.
  7. Optional: In the
    Description
    field, type a description for the URL.
  8. If you don’t want any of the FPS detection features to run on the web page of the URL receiving automatic transactions data, disable the
    Inject JavaScript
    setting.
  9. If the URL from which the HTTP request is being sent contains SPA views and you want the URL receiving automatic transactions data to inherit those views, select the
    Enabled
    check box by Views.
  10. Select the
    Enabled
    check box by Parameters.
  11. If you have assigned Request Signatures to the URL from which the HTTP request is being sent and you want the URL receiving automatic transactions data to inherit them, select the
    Enabled
    check box by Request Signatures.
  12. Click the
    Clone
    button in the Clone URL pop-up screen.
    Once the new URL is created, there is no further dependency on the source URL and any future changes made to the source URL are not inherited by the new URL.
After configuring a URL for receiving automatic transactions data, you should configure data manipulation detection on the URL or view.