Micro-Deposit Verification
How Harbor reports the small test deposits that other banks send to verify a deposit account.
To check that a deposit account is real and belongs to the named holder, an outside bank or platform may send a few cents to it. Harbor tells you with the bank_account.micro_deposit.received webhook, so you can read the amount and complete the check.
How It Works
What happens when a micro-deposit arrives.
- An outside bank sends a few cents by ACH Push to a deposit account, then asks the account holder to confirm the amount.
- Harbor sends you the
bank_account.micro_deposit.receivedwebhook, and an email. You read the amount and confirm it. - A micro-deposit isn't a payment. It never becomes an on-ramp transfer, so there is no
transfer.deposit.createdevent. Nothing is converted, no hold is placed, and your balance doesn't change.
Micro-Deposit Event
When Harbor sends the event.
Harbor sends bank_account.micro_deposit.received when all of these are true:
- The deposit is an inbound ACH Push from an external bank. ACH pulls and wires never qualify.
- It lands on a deposit account Harbor issued to you or your Customers.
- The amount is above zero and below USD 1.00. Exactly 1.00 doesn't qualify.
- It's the first time Harbor has seen this deposit.
- You have an enabled webhook subscription that includes the event.
If the account number doesn't match any account, no webhook is sent. A missing webhook means "not matched", not "handled quietly".
Micro-Deposit Subscription
How to receive the event.
- Subscribe with
bank_account.micro_deposit.received, or withbank_account.*. - Subscribing to
deposit_account.*doesn't deliver this event.
See Webhooks for how to create a subscription.
Micro-Deposit Payload
What the webhook contains. The fields sit at the top level of the request body, not inside a data object.
{
"object": "bank_test_deposit",
"event": "bank_account.micro_deposit.received",
"account_number": "312345678901",
"amount": "0.24",
"currency": "USD",
"description": "ACCTVERIFY",
"received_at": "2026-07-30T03:08:10+00:00",
"crb_ach_transaction_id": 1234,
"customer_id": "cus_EXAMPLEcustomerid00000000000000000000000"
}| Field | Type | Description |
|---|---|---|
object | string | Always bank_test_deposit. |
event | string | Always bank_account.micro_deposit.received. |
account_number | string | The full deposit account number that received the money. Keep any leading zeros. |
amount | string | The amount received, for example "0.24". This is the value the verifying bank asks you to confirm. Parse it as a decimal, not a float. |
currency | string | Always USD today. |
description | string or null | The descriptor the sending bank wrote, for example ACCTVERIFY. null if they wrote none. |
received_at | string or null | When Harbor recorded the deposit, in ISO 8601 with a time zone offset. |
crb_ach_transaction_id | integer or null | The ACH transaction ID. Quote it to support if a deposit needs tracing. |
customer_id | string or null | The Customer that holds the deposit account. |
Micro-Deposit Email
What the email says, and who gets it.
- Customer account: the email goes to the Customer, with your business owner copied.
- Your own KYC: if your application handles KYC itself, it goes to your application's registered email address.
- Content: the amount, the sender's descriptor and the last four digits of the account number. The subject is
Micro Deposit of <amount> <currency> Received | OwlPay.
The Customer may see the email before your integration processes the webhook. Make sure your support team knows about it.
Sandbox Testing
How to try a micro-deposit in Sandbox.
Simulate a payment on an active deposit account, with an ACH_PUSH under USD 1.00:
POST /api/v1/deposit_accounts/{deposit_account_id}/simulate_payment
{
"amount": 0.5,
"method": "ACH_PUSH",
"sender_name": "Bank Verify"
}The response is 202, with classified_as set to micro_deposit. Harbor sends the event within seconds, and creates no transfer.
In Sandbox, one simulated deposit can send the event twice, a few seconds apart. Deduplicate as described in the notes below.
Notes
- Duplicates: use
account_numberpluscrb_ach_transaction_idto detect duplicates. Don't usereceived_at. - Reply: answer with any
2xxwithin 10 seconds. Harbor retries a non-2xxreply or a timeout. A404is treated as a dead endpoint and isn't retried. - New fields: ignore fields you don't recognize. Harbor may add new fields.
- Descriptor: many senders write
ACCTVERIFY, but the wording is theirs and has no meaning for Harbor.
Updated about 1 month ago