# Verification retry flows

**URL:** <https://discuss.dwolla.com/t/verification-retry-flows/9436>\
**Category:** Customers\
**Created:** [December 26, 2023, 5:37pm UTC](https://discuss.dwolla.com/t/verification-retry-flows/9436 "2023-12-26T17:37:14Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![lucio](https://avatars.discourse-cdn.com/v4/letter/l/ec9cab/32.png) [@lucio](https://discuss.dwolla.com/u/lucio)\
**Post date:** [December 26, 2023, 5:37pm UTC](https://discuss.dwolla.com/t/verification-retry-flows/9436/1 "2023-12-26T17:37:14Z")

</div>

In sandbox, we’re testing our verified customer RETRY flows. So I can put a verified customer in a RETRY state by putting RETRY in the first name. So now I want to either

- Update the customer into a verified state
- Update the customer into a KBA state

How do I cause these outcomes? The online docs don’t go into this.

Also, when handling these RETRY flows, we use the UpdateCustomer endpoint, not the CreateCustomer endpoint, correct?

---

<div class="post-metadata">

**Author:** ![shreya](https://sea2.discourse-cdn.com/dwolla/user_avatar/discuss.dwolla.com/shreya/32/2154_2.png) [@shreya](https://discuss.dwolla.com/u/shreya)\
**Post date:** [December 26, 2023, 9:45pm UTC](https://discuss.dwolla.com/t/verification-retry-flows/9436/2 "2023-12-26T21:45:21Z")

</div>

Hi @lucio,

Yes, you’re correct. When handling `RETRY` flows, you should use the `UpdateCustomer` endpoint, not the `CreateCustomer` endpoint.To update a customer into a `verified` state, you need to call the `UpdateCustomer` endpoint and submit full identifying information with an updated firstName value and full SSN. Here is an example request:

```auto
POST https://api-sandbox.dwolla.com/customers/{customerId}
Content-Type: application/vnd.dwolla.v1.hal+json
Accept: application/vnd.dwolla.v1.hal+json
Authorization: Bearer {yourAccessToken}

{
  "firstName": "John",
  "lastName": "Doe",
  "email": "jdoe@nomail.com",
  "ipAddress": "10.10.10.10",
  "type": "personal",
  "address1": "221 Corrected Address St.",
  "address2": "Apt 201",
  "city": "San Francisco",
  "state": "CA",
  "postalCode": "94104",
  "dateOfBirth": "1970-07-11",
  "ssn": "123-45-6789"
}

```

(Source: [Update a customer](https://developers.dwolla.com/api-reference/customers/update#request-and-response))

To update a customer into a `KBA` state, the customer must fail to be systematically identity-verified after their second attempt to retry their information. You will need to ask [support@dwolla.com](mailto:support@dwolla.com) to enable KBA for your account(s) in Sandbox and/or Production for that. The customer will then be placed in a `kba` status and will be required to successfully answer at least three out of four knowledge based authentication (KBA) questions in order to pass verification. You can simulate this in the Sandbox environment by answering the questions with any answer choices other than “None of the above” or “I have never been associated with this vehicle”. As a result, the Customer will be placed in a document status and the `customer_verification_document_needed` event is triggered.

(Source: [Simulate KBA verified and failed events](https://developers.dwolla.com/docs/balance/testing/customers#simulate-kba-verified-and-failed-events))