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

# FAQ

## Getting Started

> [accordion] What is Grid and who is it for?
>
> Grid is a low-level payment infrastructure API that enables businesses, financial institutions, and developers to send and receive payments globally across fiat currencies, stablecoins, and Bitcoin.
>
> Grid is ideal for:
>
> * Fintech companies building payment products
> * Businesses sending international payouts
> * Platforms enabling P2P payments
> * Companies offering crypto on/off-ramps
> * Businesses distributing rewards or incentives

> [accordion] How do I get started with Grid?
>
> **1. Create an Account**
>
> Go to [app.lightspark.com](https://app.lightspark.com) to create your account and access the Grid dashboard.
>
> **2. Generate Sandbox API Keys**
>
> Generate your sandbox API keys from the dashboard and start building and testing your integration.
>
> **3. Go to Production**
>
> Once testing is complete, reach out to your Lightspark contact to receive production credentials and launch with real transactions.

> [accordion] Do I need to know about cryptocurrency to use Grid?
>
> No. Grid handles all on-chain operations, wallet management, and crypto conversions behind the scenes. You interact with a simple REST API using familiar concepts like customers, accounts, and transactions. Bitcoin and stablecoins are just another payment rail that Grid manages for you automatically.

## Building your integration

> [accordion] Can I test without moving real money?
>
> Yes. The sandbox lets you test your integration without making real payments. Use sandbox API credentials and the simulation tools to exercise payment outcomes before going live. See [sandbox testing](https://agents-docs.lightspark.com/api-reference/sandbox-testing.md).

> [accordion] Do sandbox and production use different APIs?
>
> They use the same base URL. Your API token determines which environment a request uses. Production access is arranged with your Lightspark contact after testing. See [environments](https://agents-docs.lightspark.com/api-reference/environments.md).

> [accordion] Which currencies and payment rails can I use?
>
> Check [currencies and payment rails](https://agents-docs.lightspark.com/platform-overview/core-concepts/currencies-and-rails.md) for coverage. Your platform's configuration determines which currencies are enabled for your integration. Use `GET /config` to check your supported currencies and their customer information requirements.

> [accordion] How do I know whether a payment has completed?
>
> Use webhooks to receive payment status changes, and retrieve the transaction when you need its current state. Verify webhook signatures and handle duplicate events using the event ID. See the [transaction lifecycle](https://agents-docs.lightspark.com/platform-overview/core-concepts/transaction-lifecycle.md) and [webhook guide](https://agents-docs.lightspark.com/api-reference/webhooks.md).

> [accordion] Can I start issuing cards as soon as I have API credentials?
>
> Cards must be enabled for your platform, and you need to complete card-issuer onboarding before launching. The [implementation overview](https://agents-docs.lightspark.com/cards/onboarding/implementation-overview.md) covers the setup and prerequisites.

## Licensing and customer verification

> [accordion] Is Lightspark licensed?
>
> Yes. Lightspark's regulated entities hold licenses for financial services, including money transmission in the US and electronic money and crypto-asset services in Europe. See the [licenses page](https://www.lightspark.com/licenses) for the entities, jurisdictions, and licenses. Coverage depends on the service and where you operate; [contact our team](https://www.lightspark.com/contact) to discuss your setup.

> [accordion] Who handles customer verification?
>
> It depends on your platform's setup. Lightspark provides hosted and API-based KYC/KYB flows for platforms that rely on Lightspark for verification. Regulated platforms follow a separate onboarding path. Requirements vary by customer type, region, and currency. See [customer configuration](https://agents-docs.lightspark.com/payouts-and-b2b/onboarding/configuring-customers.md) for both paths and the information to collect.


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