---
title: Verify a single account
description: Submit a request to verify a bank account through the DebiPay checks API.
openapi: /openapi/debi-pay-api.yaml POST /api/v1/checks/verify/account
---

> **For AI agents:** the complete documentation index is at [llms.txt](/llms.txt). Append `.md` to any page URL for its markdown version.

This endpoint validates a single account by sending the verification request to DebiPay's checks service. It is useful when you want to confirm account details before moving forward with a mandate, payment, or payout flow.

<Info>
Use this operation when you need an immediate verification result for one account rather than a whole batch.
</Info>

## When to use this endpoint

- Verify a customer or merchant bank account before onboarding.
- Check an account ahead of a transaction or mandate setup.
- Support manual review workflows for account validation.

## Request details

The current OpenAPI definition does not expose a detailed request body schema for this operation, so the generated request panel should be used to inspect the exact payload shape required by your environment.

## Response handling

The response contains the verification outcome returned by DebiPay. Review the generated schema for the exact fields and status values returned by your API instance.

<Tip>
For higher-volume use cases, prefer the batch verification endpoints instead of submitting one account at a time.
</Tip>

## Related pages

- [Get verification results for a batch](./checks-verification-batch-id-accounts-get)
- [Submit a batch of accounts for verification](./checks-verify-batch-id-accounts)
- [Upload accounts for batch verification](./checks-verify-upload-accounts)


---

📦 **OpenAPI specs:** Every OpenAPI specification referenced by this documentation is available as a single download — https://mutex-core-apis.jamdesk.app/api-specs.zip