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

# Renew a Bank Consent: Length, Reminders and Lapse

> How long a bank consent lasts, when Didit reminds you, what the renew call answers, and what happens when the consent lapses.

A bank consent lasts as long as the bank allows, and then it has to be renewed by the person.
Didit tells you before it ends and gives you a renew call for the same connection.

## How long it lasts

* The bank and the route set the end date, at most the `consent_days` you asked for.
* Every connection shows its real dates in `consent.expires_at` and `consent.renew_by`.
* The institution shows the longest consent the bank allows in `consent_days_max`.
* Never promise your users a fixed number of days: say "until" the date on the connection.

## Know in advance

`bank.connection.consent_expiring` is sent 14, 7 and 1 day before the end.
You can also list connections that end soon:

```bash theme={null}
curl "https://verification.didit.me/v3/bank/connections/?status=active&consent_expires_before=2026-12-15" \
  -H "x-api-key: $DIDIT_API_KEY"
```

## Renew

```bash theme={null}
curl -X POST https://verification.didit.me/v3/bank/connections/$CONNECTION_ID/renew/ \
  -H "x-api-key: $DIDIT_API_KEY" -H "content-type: application/json" \
  -d '{ "redirect_url": "http://localhost:3000/bank/return" }'
```

It answers `201` with a renew link, or one of these:

| Answer | Meaning |
| - | - |
| `409 renewal_not_needed` | More than 30 days are left. Try again later. |
| `409 renewal_window_expired` | `consent.renewable_until` has passed. The person connects again with a new link. |

The page where the person completes a renewal is not available yet, so do not send people to a renew link today.
Until it is, use the reminders above to know when a consent ends.

## If the consent lapses

* The connection becomes `renewal_required` with `status_reason: consent_expired` or `bank_requires_sign_in`.
* You can still read what was synced, nothing is synced or charged, and `bank.connection.renewal_required` is sent.
* After `consent.renewable_until` it is `revoked` with `status_reason: consent_lapsed`, and the person connects again.

## Related

* [Connections](https://docs.didit.me/core-technology/bank-verification/connections.md)
* [Continuous bank feed for accounting](https://docs.didit.me/use-cases/bank-data-for-accounting.md)
* [Data, consent and deletion](https://docs.didit.me/core-technology/bank-verification/data-consent-and-deletion.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.