BankingIdentity

Address Updates

Validate a new email address before it replaces the one on file for a customer's account.

Email validity · 1 credit per lookup · no monthly fee

Update email

s.lane@oldjob.com
sara@newmail.com

The problem

A customer updates the email on their account, and fat-fingers it. Now statements, alerts and password resets go to an address that doesn't exist, and the customer has effectively locked themselves out without knowing it. In banking, that's a compliance incident waiting to happen.

With Encrata

Verify the new address before it replaces the old one. Encrata confirms the mailbox exists and accepts mail in real time, so the update flow can reject dead addresses on the spot and keep the old address active until a working replacement is confirmed.

How it works

1

Send the address

Call the validity endpoint with the email address at the moment it enters your system, a form, an import, a checkout.

2

We ask the mail server

Encrata checks syntax, domain and mailbox directly with the receiving server, and flags disposable and typo domains.

3

Act on the verdict

Accept, reject or suggest a correction based on a clear valid / invalid / catch-all / risky verdict. One credit per check.

One call, structured answer

Address Updates runs on the email validity lookup at 1 credit per lookup. Same API key, same JSON shape as every other Encrata lookup.

  • Answers come from the mail server itself, not a guess from patterns
  • Disposable and throwaway domains are flagged before they cost you anything
  • 1 credit per check, cheap enough to run on every address you touch
  • Cached results are free, so repeated checks never double-charge
Terminal
curl -X POST "https://encrata.com/api/agent/validate" \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{"email": "sara@acme.com"}'
response.json
{
"email": "sara@acme.com",
"status": "valid",
"reason": "deliverable",
"disposable": false,
"confidence": "high",
"provider": "google",
"message": "Mailbox exists and accepts mail, safe to send.",
"credits": 1
}

Verify before the swap

The safe pattern is verify-then-swap: when a user submits a new address, validate it, send a confirmation link to the new mailbox, and keep the old address active until the link is clicked. Encrata's check catches the dead-on-arrival addresses instantly, so the user fixes typos in the moment instead of discovering the problem at their next password reset.

An audit trail for free

For regulated products, log the verification verdict alongside the change: 'address updated after deliverability confirmation' is an audit-trail entry that closes questions before they're asked. The support impact is real too, account-recovery escalations drop when the recovery path can't silently point at a mailbox that never existed.

More email validity use cases

View all
Start with 500 free credits
$curl https://encrata.com/api/agent/lookup -H "Authorization: Bearer YOUR_API_KEY" -d '{"e": "satya@microsoft.com"}'