Layer 1 copy

Use-case

This guide helps companies that have a single payment form to accept donations or to accept payments for services that do not require fulfillment of items prevent chargebacks.

Send User Events

A core integration includes the following (when applicable):

Integrate your website
Integrate your mobile app
Integrate your events
When you process a payment
  1. When you process a payment, send a $transaction event with
    • $transacton_status : '$pending'
    • $transaction_type : '$sale' (or '$authorize' if you authorize before capturing
    • Use the customer's email address (lowercase) as $user_id if they're not logged in to an account.
    • Set the $amount field to the amount they are donating.
    • Fill out as many fields in the $payment_method object as possible.
  2. Check the response from the $transaction event for our risk assessment (see the 'Make Decisions' section below).
  3. If you proceed with the transaction, send another $transaction event with
    • $transacton_status : '$success', '$failure' (based on response from the payment gateway)
    • $transaction_type : '$sale' (or '$authorize' - the same as before)
    • Fill out all fields from the previous $transaction event.
  4. If you do a separate authorization, send a third $transaction event with
    • $transaction_type : '$capture'
    • Fill out all fields from the previous $transaction events.
Additional Events

The following events can be sent to capture a more complete picture of users when applicable: $update_account (whenever a user updates their account information, e.g. adds payment information or changes contact info), $login, $logout.

Send Feedback to Sift

One of the key strengths of the Sift Science platform is that as you give it feedback it continues to learn and adapt to patterns. By providing continuous feedback on who your good and bad users are, we will evolve our detection and improve the accuracy of risk scores. You’ll be able to stop bad actors even as they change their attack vectors. In addition to sending an optional historical backfill:

  • Create a Feedback focused Workflow where you review high scoring users and tell us how well we are predicting your fraudsters.
  • If you are already doing manual review in your existing system, just send the outcome of each review to our Labels API

Once you’re up and running with Sift, continuing to send feedback will improve your score accuracy in real-time, catching bad users as soon as they appear. This is an important part of a successful integration.

Make Decisions with Sift

Scores are an indication of how risky a user is for a given abuse type. You can use these scores as a means to block bad users, add friction to users you are unsure about (e.g., SMS verification), and let good users sail right through. You'll want to make this check at your $transaction event.

The two ways to do this are:

  • Create a Sift Workflow You can build application logic into Sift with our Workflow product. Workflows let you set up criteria that get evaluated whenever specified events occur. Learn more in our Workflows tutorial.
  • Build application logic in your system An alternate approach is to request abuse specific risk scores to be returned in the response of the user events you send. See our API documentation

Any questions? We're happy to talk it through.