Enable users to enter CVV and ZIP codes to finish a scanned card entry
Enable users to enter all card details
Track and log signals about the device and user, and send these signals back to Bouncer
Note: The Bouncer SDK will not directly expose whether this was a legitimate scan of a real card to the client App. It’ll be up to the client App to make a subsequent server-to-server call to get the authentication results.
Role of the Bouncer Server:
Your server needs to make two API calls to Bouncers server (1) when users tokenize a card and (2) at transaction time to get a fraud score:
/insight/v1/tokenize(server-to-server): Called when the App Server tokenizes a card successfully
/insight/v1/score (server-to-server): Risk assessment at transaction time, called for all transactions