Payrails Fraud SDK

SDK providing abstraction on top of different fraud providers

Stripe Radar with more than one Stripe account

A Radar session is only valid for the Stripe account whose publishable key minted it, and the account is chosen when the payment is routed, after the session has been created. If you process through more than one Stripe account, configure one entry per account, each with that account's own publishable key and the providerConfigId of the matching Payrails provider config:

await FraudSDK.load([
  {
    provider: FraudProvider.STRIPE_RADAR,
    publishableKey: 'pk_live_accountA...',
    providerConfigId: '11111111-1111-4111-8111-111111111111',
  },
  {
    provider: FraudProvider.STRIPE_RADAR,
    publishableKey: 'pk_live_accountB...',
    providerConfigId: '22222222-2222-4222-8222-222222222222',
  },
]);

stripe.js loads once regardless of how many entries you configure, and one Radar session is minted per entry. The Web SDK sends them all when the payment is authorized and Payrails uses the one matching the account it routed to.

Each entry's publishable key must belong to the account its providerConfigId points at. A mismatched pair is not rejected up front and instead surfaces as Stripe declining the payment with No such radar session. With a single Stripe account, omit providerConfigId and nothing changes.

Changelog

1.9.0 Stripe Radar sessions can be configured per Stripe account

1.5.0 Support for Forter and Ravelin added