Skip to main content

Merchants

You integrate Fraugster before authorization happens. By doing that, you weed out fraud before sending transactions to your bank for authorization. You send only approved transactions and thus cut unnecessary authorization costs.

Note

We recommend including transaction payment details in your first API request. If this data is available, Fraugster gives each transaction a more accurate decision and score. However, the availability of payment method data depends on your PCI compliance and the way your integration with the payment gateway works. If you are not PCI compliant and cannot include payment method data in your API request, reach out to the Customer Support team at [email protected] to discuss the performance of our product.

Your integration should cover four main events that must happen for each transaction reaching the Fraugster API:

  1. Submit transaction details in your first API request. Each transaction reaches Fraugster in the form of datapoints. See the full list of available datapoints in Fraugster datapoints.
  2. Receive a fraud check response from Fraugster.
  3. Send the sync status update to Fraugster right after receiving the API response.
  4. Send the async status update to Fraugster when more information becomes available.

Points 1-3 must happen within the Fraugster API. Point 4 can happen either via an API call, or by sending batch files (see Async status updates).

What is Fraugster's role in the data flow?​

To answer this question, let's have a look at a detailed use case.

  1. An end customer attempts a payment from a browser. You collect data about the transaction and the payment method. The format of the payment method data you collect depends on your PCI compliance and integration with your payment gateway. If you cannot collect payment method data, please refer to our recommendation above.

  2. You send the collected data to Fraugster for a fraud check in an API request.

  3. You receive an API response in real time. It contains a recommendation on whether the transaction is approved or declined.

  4. Based on the API response, you have the following options:

    1. If Fraugster approves the transaction, you send it to your payment gateway, which then passes it on to the acquirer and issuing bank for a final authorization.
    2. If Fraugster declines the transaction:
    • You return the sync status update frg_declined to confirm that you declined the transaction based on Fraugster's recommendation.
    • You do not return the sync update frg_declined to indicate that you sent this transaction for authorization in spite of Fraugster's recommendation.

  5. You receive a response from your payment gateway, indicating whether the transaction was approved or declined.

  6. You send a sync status update indicating whether the issuer approved the transaction.

    The sync status update is required. It has a determined set of values that an API call can contain:

  • approved - to confirm that the transaction was approved by the issuer.

  • declined - to let us know that the issuer rejected the transaction.

  • declined_fraudscreening - to let us know if the transaction was declined by a different fraud detection solution (only if there is a second fraud detection system in place).

  • error - to inform us that the transaction wasn't authorized due to an error.

    Important

    The statuses approved and declined always require additional information to be sent with them. Read more in Update transactions.

  1. If more information becomes available about the transaction, send an async status update to notify Fraugster. It is important for Fraugster to be aware of any additional status updates in order to maximize the Engine performance. Fraugster provides a wide range of values you can send to update us. Read more in Update transactions.

    The most important async status updates are the ones that indicate if a transaction is fraudulent:

  • chargeback - this status update is relevant for card transactions.

  • fraud_confirmed - this status is suitable for non-card transactions. Inform Fraugster if a transaction is concluded as fraudulent by you.

  • debt_collection_loss - this status is suitable for payment upon invoice. Confirm if you have written off a transaction as a loss after the debt collection process.

    Important

    The statuses chargeback and debt_collection_loss always require additional information to be sent with them. Read more in Update transactions.

Read more on how to send status updates in:

Last updated on