> ## Documentation Index
> Fetch the complete documentation index at: https://docs.lightspark.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Launch checklist

> Everything Lightspark reviews before you move from sandbox to production

Work through this checklist before you request production access. Lightspark reviews each item and confirms your platform is ready to move real funds.

> [!WARNING]
>
> Lightspark Legal approval is a hard gate on launch. You can't go live or onboard any end user until Legal has reviewed and approved your consent flow. Start assembling this evidence while you build, not after.

## Commercial and compliance prerequisites

Complete these before you build the consent and disclosure flows below. They gate everything else.

| Item | What Lightspark confirms |
| - | - |
| Signed contract | Your agreement with Lightspark is executed, with legal and compliance sign-off on both sides. |
| KYB complete | Your business has passed Know Your Business verification. |
| UBO verification complete | Every ultimate beneficial owner of your business is identified and verified. |
| Funds flows validated | Lightspark has reviewed and signed off on how money moves between your platform, your end users, and Grid for each product you're launching. |

## End user agreements

Present each of these agreements in your onboarding flow and capture affirmative consent before you onboard the end user.

| Agreement | Where to get it |
| - | - |
| Lightspark terms of service | [End User Terms](https://www.lightspark.com/legal/grid/enduserterms) |
| Lightspark e-sign consent | [E-Sign Consent](https://www.lightspark.com/legal/grid/enduserterms#e-sign-consent) |
| Lightspark privacy policy | [Privacy Policy](https://www.lightspark.com/privacy-policy) |
| Partner bank accountholder agreement | Send your fee schedule to your Lightspark representative. Lightspark generates the agreement from it for you to display. |
| Partner bank privacy policy | [Your Privacy Rights](https://www.lead.bank/legal/privacy) |

> [!WARNING]
>
> Link the e-sign consent to its own section of the End User Terms, as in the table above. A link to the full terms doesn't make the consent prominent enough. Your end user has to see and affirm it directly.

### Sample consent screen

Present the agreements as two separate affirmative actions: one consent to receive records electronically, one acceptance of the terms. Each bracketed item links to the live agreement.

```text Consent screen copy theme={null}
Account provided by [Partner Bank].

☐ I consent to receive all disclosures, agreements, and records electronically.
  Lightspark [E-Sign Consent]

☐ I agree to Lightspark's [Terms of Service] and [Partner Bank]'s
  [Accountholder Agreement], and I acknowledge Lightspark's [Privacy Policy]
  and [Partner Bank]'s [Privacy Policy].
```

Use unchecked checkboxes or an equivalent affirmative action. Pre-checked boxes and implied consent are not acceptable.

### Record each acceptance

If you're an unregulated platform moving funds on Lightspark's money transmitter licenses, send evidence of acceptance as `endUserTermsConsent` when you create the customer. For the field reference and the API behavior when consent is missing, see [Disclosures](https://docs.lightspark.com/payouts-and-b2b/onboarding/disclosures.md).

## Transaction disclosures and records

Beyond onboarding, you owe end users disclosures and records over the life of the account.

| Requirement | When it applies | Where to start |
| - | - | - |
| Reg E Part B pre-transaction disclosure | Before an end user confirms an international remittance. Shows the exchange rate, fees, and the amount the recipient receives. | Quote response fields, see [Assessing fees](https://docs.lightspark.com/payouts-and-b2b/payment-flow/assessing-fees.md) |
| Receipts | Every completed transaction. | [Receipts](https://docs.lightspark.com/payouts-and-b2b/payment-flow/receipts.md) |
| Periodic statements | On the cadence your product commits to, for end users holding a balance. | [Periodic statements](https://docs.lightspark.com/payouts-and-b2b/payment-flow/statements.md) |
| ACH mandate | Before you debit an end user's bank account by ACH. Captures their authorization for the debit. | [External accounts](https://docs.lightspark.com/payouts-and-b2b/depositing-funds/external-accounts.md) |

## If you're launching Cards

Card programs carry the same commercial prerequisites above, plus one more agreement.

* **Cardholder agreement** at card sign-up. Present it and capture acceptance before you issue the card.

For the card issuing flow, see the [Cards](https://docs.lightspark.com/cards/index.md) documentation.

## Technical readiness

Confirm your integration handles production traffic and failure modes.

* **Webhooks** are registered, signature verification is in place, and your handler is idempotent. See [Webhooks](https://docs.lightspark.com/payouts-and-b2b/platform-tools/webhooks.md).
* **Idempotency keys** are sent on every request that moves money, so a retry can't double-send.
* **Error handling** covers rejected quotes, expired quotes, and failed payments, with each surfaced to the end user. See [Error handling](https://docs.lightspark.com/payouts-and-b2b/payment-flow/error-handling.md).
* **Reconciliation** ties every Grid transaction back to a record in your ledger. See [Reconciliation](https://docs.lightspark.com/payouts-and-b2b/payment-flow/reconciliation.md).
* **Monitoring and alerting** cover webhook delivery failures and stuck transactions.
* **Sandbox UAT** exercises your full flow end to end, including the failure paths. See [Sandbox testing](https://docs.lightspark.com/payouts-and-b2b/platform-tools/sandbox-testing.md).

## What to submit to Lightspark

Send these items to your Lightspark representative to request review.

**1. Screenshots of your consent and disclosure screens**

Submit screenshots of your implemented interface showing every agreement and disclosure in the tables above. Lightspark Legal reviews them against the sample consent screen above. Include:

* **The consent screen**, showing each agreement linked and the unchecked boxes the end user has to check.
* **Each disclosure** in the screen where the end user sees it.

Where the content is hosted on a page of your own, include the link alongside the screenshot.

**2. A recording of your sandbox flow**

Record a screen capture of the complete end user experience in sandbox, from a new end user through a completed payment. Cover:

* Onboarding, including the consent screen and every agreement link
* Identity verification (KYC or KYB)
* Adding a funding source or payout account
* Creating and confirming a payment, including the pre-transaction disclosure
* The completed payment and the receipt the end user receives

A single unedited recording is preferred. Narration is optional.

**3. Your policies and audit reports**

Send PDF copies of:

* Your privacy policy
* Your terms of service
* Your information security policy
* Your most recent ISO, SOC 2, or PCI audit reports, if you have them
* Your most recent penetration test report, if you have one

If you contact end users by phone call or text message, also send your Telephone Consumer Protection Act (TCPA) disclosure.

> [!TIP]
>
> After Lightspark approves your submission, Lightspark creates a production platform under your existing account and configures the fees defined in your order form. You then generate production API keys for that platform from the dashboard.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.