2 ms·
> Business model > Pricing was to be charged per successful request (accept) > and similar to Sift Science in terms of a handful of cents > per request. Reject
by diggan 10y ago
> Business model
> Pricing was to be charged per successful request (accept) > and similar to Sift Science in terms of a handful of cents > per request. Reject requests were to be free.
That strikes me as a weird way of doing the pricing. If a request was successful but should really have been rejected, the user is paying. If the request was denied but should really have been successful, the user of the service (of the fraud detection service) is loosing.
Also, this part sounds really scary when you're dealing with payments:
> . It essentially just monkey patches Stripe.card.createToken() to call our api first
Would probably brake the payment as well if Stripe is updating the script (and since the script HAS to be loaded from their domain, nothing you can "guard" against)
- deleted 10y ago[deleted]