Skip to main content
Work through this checklist before you request production access. Lightspark reviews each item and confirms your platform is ready to move real funds.
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.

​
End user agreements

Present each of these agreements in your onboarding flow and capture affirmative consent before you onboard the end user.
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.
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.
Consent screen copy
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.

​
Transaction disclosures and records

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

​
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 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.
  • 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.
  • Reconciliation ties every Grid transaction back to a record in your ledger. See Reconciliation.
  • 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.

​
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.
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.