> For the complete documentation index, see [llms.txt](https://docs.neobanc.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.neobanc.com/quickstart.md).

# Quickstart

Create your first bill payment in three steps. You'll need an API token from your [API Partner Dashboard](https://app.neobanc.com/api-dashboard/api-keys) (format `nbapi_<64 hex chars>`), passed as a Bearer token on every request.

Use the sandbox base URL `https://sandbox.neobanc.com/v1` while integrating, then switch to `https://api.neobanc.com/v1` for production.

## 1. Find the payee

Search the biller catalog for the company your user wants to pay. Partial names work.

```bash
curl -X POST https://sandbox.neobanc.com/v1/payees/search \
  -H "Authorization: Bearer $NEOBANC_API_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{ "search": "enmax", "limit": 10 }'
```

Use the exact `name` from the response in the next steps.

## 2. Validate the account number

Check the user's account number against the expected format for that payee — the same validation Neobanc's own payment flow applies. This catches typos before money moves.

```bash
curl -X POST https://sandbox.neobanc.com/v1/payees/validate-account \
  -H "Authorization: Bearer $NEOBANC_API_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{ "payeeName": "ENMAX ENERGY CORPORATION", "accountNumber": "1234567890" }'
```

## 3. Create the payment

```bash
curl -X POST https://sandbox.neobanc.com/v1/create-payment \
  -H "Authorization: Bearer $NEOBANC_API_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "paymentType": "bill",
    "userName": "John Doe",
    "userEmail": "john.doe@example.com",
    "amount": 125.50,
    "dueDate": "2026-04-15T00:00:00.000Z",
    "payeeName": "ENMAX ENERGY CORPORATION",
    "billType": "Electricity",
    "accountNumber": "1234567890",
    "paymentMethod": "interac"
  }'
```

The response includes a 12-digit `identificationNumber`. Your user must include this number in the description of their Interac e-transfer — that's how Neobanc matches the incoming funds to the payment. Once matched, the payment is processed and you'll receive a `payment.completed` [webhook](/api-reference/webhooks.md).

## Next steps

* Browse the full [Payments](/api-reference/payments.md) and [Payees](/api-reference/payees.md) reference — every endpoint has an interactive "Test it" panel.
* Configure [webhooks](/api-reference/webhooks.md) to get notified when payments are created, completed, or failed.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.neobanc.com/quickstart.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.