PayFanout API reference
    Preparing search index...

    Interface PaysafeClientAdapterConfig

    interface PaysafeClientAdapterConfig {
        apiKey: string;
        cspNonce?: string;
        environment: "sandbox" | "live";
        getPaysafeGlobal?: () => PaysafeJsLike | undefined;
        loadScript?: (url: string) => Promise<void>;
        paymentMethods?: PaymentMethodCapability[];
        sdkUrl?: string;
        threeDs?: Record<string, unknown>;
    }
    Index
    apiKey cspNonce? environment getPaysafeGlobal? loadScript? paymentMethods? sdkUrl? threeDs?
    apiKey: string

    Public (single-use-token) Base64 API key — safe for the browser, holds no secrets.

    cspNonce?: string

    A Content-Security-Policy nonce for the Paysafe.js <script> the adapter injects, set as its nonce attribute before the tag is inserted, so a script-src that allows scripts by nonce without 'strict-dynamic' runs it. Paysafe.js reads no nonce itself: the wallet SDKs it loads (Google Pay, Apple Pay, Paze) and the <style> elements it adds (its 3-D Secure and redirect overlays) carry none. Pass the value alone, as in the policy's 'nonce-<value>' source; the constructor refuses anything else. The adapter never reads a nonce from the page, and a loadScript seam loads the script without it.

    environment: "sandbox" | "live"

    Explicit; mapped to Paysafe's TEST/LIVE.

    getPaysafeGlobal?: () => PaysafeJsLike | undefined
    loadScript?: (url: string) => Promise<void>

    Test seams. loadScript is called again by the next loadSdk() after an attempt that rejects or leaves the SDK global missing, so it must be safe to call more than once.

    paymentMethods?: PaymentMethodCapability[]

    Account capabilities vary per merchant account/currency — override the conservative default.

    sdkUrl?: string
    threeDs?: Record<string, unknown>

    Passed through to tokenize() so 3DS challenges run inline (iframe), never full navigation.

    Settings
    Member Visibility

    On This Page
    Properties