Skip to main content

Overview

A DraftKings-style deposit presents the customer with an input form where they can enter any amount they’d like to deposit. This is the standard experience used by sports books and gaming platforms. Every Soap API request is authenticated with a bearer token in the Authorization header:
Your API key is in the Soap Dashboard under the Developers section. It looks like key_.... Requests with a missing or invalid API key return 422 — never 401 — with a JSON error field, usually {"error": "API key not found."}. Branch on the status code rather than the message: GET /api/v1/device_pings/latest_geo_check does not yet return the same wording. Never expose your API key in client-side code — it is server-side only.

How It Works

  1. You create a checkout session with type: "deposit" and no fixed_amount_cents.
  2. The customer is redirected to the Soap-hosted checkout page.
  3. The customer enters their desired deposit amount and selects a payment method.
  4. Upon completion, a webhook is fired and the customer is redirected back to your app.

API Request

Key Parameters

When to Use

  • Your platform lets the customer choose how much to deposit
  • Standard gaming / sports-book deposit flows
  • Any scenario where the deposit amount is not predetermined

← Back to Create Checkout

View the full API reference for creating checkouts.