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.
Launch approval is a gate, not a formality. Lightspark enables production credentials after reviewing the agreements you present to end users, the disclosures you send, and a recording of your sandbox flow. Start assembling this evidence while you build, not after.
The agreement and disclosure requirements on this page apply to end users in the United States. For requirements in other regions, contact your Lightspark representative.

​
Commercial and compliance prerequisites

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

​
End user agreements

Which agreements you present depends on who your end user is and, for businesses, whether Lightspark Payments is licensed in the end user’s state. Present every applicable agreement in your onboarding flow and capture affirmative consent before the end user can transact.
Business end users in states where Lightspark Payments is licensed contract with Lightspark alone, so they see no partner bank agreements. Confirm which states apply to your product with your Lightspark representative.
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 two items to your Lightspark representative to request review.
1

Your terms and disclosure content

For each agreement and disclosure in the tables above, provide either:
  • A link to the live page where the content is hosted, or
  • A screenshot of the screen where the end user sees it, if the content isn’t publicly reachable.
Include the consent screen itself, so Lightspark can confirm each agreement is presented and accepted before the end user transacts.
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.
After Lightspark approves your submission, your representative enables production credentials and activates the corridors your product needs.