Bouncer Docs
Bouncer Home
Search…
Bouncer
Bouncer Scan
Credit Card OCR
Verifying High Risk Cards
Bouncer Insight
Get started
Integration overview
iOS integration guide
Android integration guide
Server integration guide
JavaScript Beacon
Bouncer labs
Secure Counting
Powered By GitBook
Server integration guide
To improve the accuracy of Bouncer's fraud detection, we recommend notifying bouncer for the following:
  • Payment Card Tokenization
  • Account Events
Your service can query Bouncer servers at any time (e.g. before allowing a purchase) for a fraud risk score for a given user.

[Required] Card tokenization and fraud score on transaction

Tokenizing a Payment Card

When the client adds a new payment method and that payment method is tokenized (e.g. through Stripe), call this endpoint from your server.
Request
Response
The request must include details about the payment instrument, including the payment method token. The request must additionally be authenticated with your API key.
POST https://api.getbouncer.com/insight/v1/tokenize
x-bouncer-auth: <your_api_key>
​
{
"user_id": String("<tokenizing_user_id>"),
"customer_id": String("<customer_stripe_id>"),
"instrument_token": String("<payment_instrument_stripe_token>"),
"instrument_last_four": String("<last_four_digits_of_payment_instrument>"),
"instrument_iin": Optional String("<first_six_digits_of_payment_instrument>"),
"client_ip": Optional String("<ip_address_of_client_adding_payment_instrument>")
}
The response will include a score from bouncer and a recommendation to challenge or allow the transaction.
HTTP 200 OK
{
"result": "ok"
}

Getting a fraud risk score

When you are ready to complete a transaction on the iOS or Android SDK make a server-to-server call from your servers to Bouncer to validate the transaction.
Request
Response
The request must include details about the transaction, including the payment instrument used, and the amount to be charged. The request must additionally be authenticated with your API key.
POST https://api.getbouncer.com/insight/v1/score
x-bouncer-auth: <your_api_key>
​
{
"user_id": String("<transacting_user_id>"),
"transaction_amount": Float(<amount_being_charged>),
"transaction_currency": String("<three_character_currency_code>"),
"customer_id": String("<customer_stripe_id>"),
"instrument_token": String("<payment_instrument_stripe_token>"),
"instrument_last_four": String("<last_four_digits_of_payment_instrument>"),
"instrument_iin": Optional String("<first_six_digits_of_payment_instrument>"),
"client_ip": Optional String("<ip_address_of_client_making_transaction>"),
"product_sku": Optional Array of Strings("<SKUs of the product purchased>")
}
The response will include a score from bouncer and a recommendation to challenge or allow the transaction.
HTTP 200 OK
{
"challenge_recommended": true,
"fraud_risk_score": 0.4
}
challenge_recommended will be a boolean indicating whether bouncer recommends challenging the transaction. fraud_risk_score will be a float between 0 and 1 (inclusive) that indicates how fraudulent Bouncer believes this transaction to be.

[Optional] Server-to-server account events

When you use Bouncer's SDKs for iOS, Android, and Web, the SDK communicates back with Bouncer's servers automatically. However, if you'd like to roll out a purely server-based implementation, you can use our Account Events APIs for this purpose.
These requests should be made after each of these events:
  • user signup
  • user login
  • user update
  • payment method added

Sign Up

Request
Response
The request must include details about the event, including the user ID and IP. The request must additionally be authenticated with your API key.
POST https://api.getbouncer.com/insight/v1/events/add
x-bouncer-auth: <your_api_key>
​
{
"event": "user_create",
"occurred_at": Long("<the time in MS since epoch when the event occurred>"),
"ip_address": String("<IP address of the client performing the action>"),
"session_id": Optional String("<the ID of the session for this user>"),
"user_id": String("<id of the user>"),
"user_name": Optional String("<username performing the event>"),
"phone_number": Optional String,
"first_name": Optional String,
"last_name": Optional String,
"full_name": Optional String,
"email": Optional String,
"shipping_address": Optional String,
"billing_address": Optional String
}
HTTP 200 OK
{
"result": "ok"
}

Login

Request
Response
The request must include details about the event, including the user ID and IP. The request must additionally be authenticated with your API key.
POST https://api.getbouncer.com/insight/v1/events/add
x-bouncer-auth: <your_api_key>
​
{
"event": "user_login",
"occurred_at": Long("<the time in MS since epoch when the event occurred>"),
"ip_address": String("<IP address of the client performing the action>"),
"session_id": Optional String("<the ID of the session for this user>"),
"success": Boolean("<whether or not the login attempt succeeded>"),
"failure_reason": String("<reason the login failed, one of the following: account_unknown, bad_credentials>"),
"user_id": Optional String("<id of the user>"),
"user_name": Optional String("<username performing the event>")
}
HTTP 200 OK
{
"result": "ok"
}

User Update

Request
Response
The request must include details about the event, including the user ID and IP. The request must additionally be authenticated with your API key.
POST https://api.getbouncer.com/insight/v1/events/add
x-bouncer-auth: <your_api_key>
​
{
"event": "user_update",
"occurred_at": Long("<the time in MS since epoch when the event occurred>"),
"ip_address": String("<IP address of the client performing the action>"),
"session_id": Optional String("<the ID of the session for this user>"),
"user_id": String("<id of the user>"),
"user_name": Optional String("<username performing the event>"),
"phone_number": Optional String,
"first_name": Optional String,
"last_name": Optional String,
"full_name": Optional String,
"email": Optional String,
"shipping_address": Optional String,
"billing_address": Optional String
}
HTTP 200 OK
{
"result": "ok"
}

Add payment method

Request
Response
The request must include details about the event, including the user ID and IP. The request must additionally be authenticated with your API key.
POST https://api.getbouncer.com/insight/v1/events/add
x-bouncer-auth: <your_api_key>
​
{
"event": "payment_method_add",
"occurred_at": Long("<the time in MS since epoch when the event occurred>"),
"ip_address": String("<IP address of the client performing the action>"),
"session_id": Optional String("<the ID of the session for this user>"),
"user_id": Optional String("<id of the user>"),
"payment_method_id": String("<customer-defined payment method ID>"),
"payment_method_type": String,
"payment_gateway": String,
"success": Boolean("<true if the payment method was added successfully>"),
"card": Optional {
"card_brand": Optional String,
"card_funding": Optional String,
"card_fingerprint": Optional String,
"card_bin": Optional String,
"card_last4": Optional String,
"card_exp_month": Optional String,
"card_exp_year": Optional String,
"card_name": Optional String,
"card_cvc_check": Optional String,
"card_zip_check": Optional String,
"card_address": Optional {
"street1": Optional String,
"street2": Optional String,
"city": Optional String,
"state": Optional String,
"zip": Optional String,
"country_iso": Optional String
}
},
"failure_type": String,
"decline_code": String,
"failure_reason": String
}
HTTP 200 OK
{
"result": "ok"
}
​
Bouncer Insight - Previous
Android integration guide
Next - Bouncer Insight
JavaScript Beacon
Last modified 1yr ago
Copy link
On this page
[Required] Card tokenization and fraud score on transaction
Tokenizing a Payment Card
Getting a fraud risk score
[Optional] Server-to-server account events
Sign Up
Login
User Update
Add payment method