> 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/api-reference/bank-accounts.md).

# Bank Accounts

Register Canadian business bank accounts that Neobanc may debit via **EFT (Pre-Authorized Debit)** to fund bill payments — instead of sending an Interac e-transfer per payment, you create payments with `paymentMethod: "eft"` and Neobanc pulls the funds directly from your registered account.

## How EFT funding works

1. Sign Neobanc's **PAD agreement** (provided during onboarding) and register the account below, confirming acceptance with `padAccepted: true` and the signatory's identity.
2. Create bill payments with `paymentMethod: "eft"` and the returned `bankAccountId`.
3. Neobanc initiates an EFT debit for the payment amount. EFT is not instant — funds typically arrive in **1–3 business days**. The payment stays `pending` until the debit completes.
4. When the debit completes, the payment transitions to `completed` (you receive a `payment.completed` webhook) and enters the next settlement batch to the biller. If the debit fails (e.g. non-sufficient funds, account closed), the payment transitions to `failed` and you receive a `payment.failed` webhook.

{% hint style="warning" %}
Under Payments Canada rules, an EFT debit can be returned by the bank **after** it initially completes (a "late failure"). If that happens after the bill was already paid to the biller, the biller-side payment stands and the amount remains owed to Neobanc under the PAD agreement.
{% endhint %}

## Register a bank account

Full account details are stored with our payment processor; Neobanc retains only the last 4 digits. Requires the `public_api:bank_accounts_manage` permission.

{% openapi src="<https://api.neobanc.com/openapi.json>" path="/bank-accounts" method="post" %}
<https://api.neobanc.com/openapi.json>
{% endopenapi %}

## List bank accounts

{% openapi src="<https://api.neobanc.com/openapi.json>" path="/bank-accounts" method="get" %}
<https://api.neobanc.com/openapi.json>
{% endopenapi %}

## Deactivate a bank account

Stops any new debits against the account (in-flight EFTs are unaffected) and serves as PAD cancellation for that account.

{% openapi src="<https://api.neobanc.com/openapi.json>" path="/bank-accounts/deactivate" method="post" %}
<https://api.neobanc.com/openapi.json>
{% endopenapi %}


---

# 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/api-reference/bank-accounts.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.