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

# Quickstart

ECRYPT handles the complexity of payments so you can focus on building. This guide walks you through the core flows to get up and running quickly.

***

## Get Started

<Card title="Setup your Sandbox" icon="key" href="https://info.ecrypt.com/">
  Create a test account and generate your API key to start building with ECRYPT
</Card>

<Columns cols={2}>
  <Column>
    <Card title="Build Online Checkout Flows" icon="browser" href="/iframe">
      Integrate hosted iFrame or Dynamic Checkout pages to accept card payments online.
    </Card>
  </Column>

  <Column>
    <Card title="Integrate Card Terminals" icon="cash-register" href="/cloud-terminal">
      Connect Cloud EMV devices to accept in-person card-present payments through the ECRYPT API.
    </Card>
  </Column>
</Columns>

<Columns cols={2}>
  <Column>
    <Card title="Run Subscriptions" icon="arrow-rotate-right" href="/subscriptions">
      Configure recurring billing, installment plans, and automated retry logic for failed payments.
    </Card>
  </Column>

  <Column>
    <Card title="Test your Integration" icon="flask" href="/testing">
      Use ECRYPT's sandbox environment and test card numbers to validate your integration end-to-end.
    </Card>
  </Column>
</Columns>

<Columns cols={2}>
  <Column>
    <Card title="Accept ACH Payments" icon="building-columns" href="ach-overview">
      Accept bank account payments alongside cards using the same token-based payment flow.
    </Card>
  </Column>

  <Column>
    <Card title="Go Live & Certification" icon="circle-check" href="/certification">
      Schedule your certification call to confirm all endpoints and flows are ready to go before going live.
    </Card>
  </Column>
</Columns>

***

## Your First API Call

Every request to the ECRYPT API requires an `X-Api-Key` header. Generate your key in **Settings > API/Security Keys**.

The first step in any payment flow is tokenizing card data. Tokenization keeps sensitive PAN data off your servers and removes your integration from PCI scope.

**Request**

```bash theme={null} theme={null}
curl --request POST \
     --url https://api.ecrypt.com/v1/tokens \
     --header 'accept: application/json' \
     --header 'content-type: application/json' \
     --header 'X-Api-Key: YOUR_API_KEY' \
     --data '{
  "credit_card": {
    "name_on_card": "John Doe",
    "account_number": "4111111111111111",
    "expires": "0135",
    "verification_value": "000",
    "postal_code": "90210"
  }
}'
```

**Response**

```json theme={null} theme={null}
{
  "token": "95222bfc-d032-4aa6-a949-3c000ad93b4b",
  "metadata": {
    "credit_card_number": "4***********1111",
    "credit_card_network": "visa",
    "credit_card_type": "credit"
  },
  "request_id": "0HNJOGLAUDGRT00000057"
}
```

The `token` value is what you pass into subsequent transaction requests in place of raw card data.

The `metadata` object returns masked card details you can display to users for confirmation. The full card number is never returned.

Use the `requestId` for support inquiries or debugging.

***

## Next Steps

1. **Environments and Keys** -- Understand sandbox vs. production and how to manage your API keys.
2. **How Payments Work** -- The full authorization, capture, and settlement lifecycle.
3. **Testing** -- Dummy card numbers and ACH account numbers for validating your integration.
4. **Webhooks Setup** -- Get notified in real time when transactions change state.