# Need Guidance on Implementing MFA OTP via Auth0 API for Post-Login Transaction Verification

**URL:** <https://community.auth0.com/t/need-guidance-on-implementing-mfa-otp-via-auth0-api-for-post-login-transaction-verification/186937>\
**Category:** Get Help\
**Tags:** mfa-api, mfa\
**Created:** [May 20, 2025, 7:28am UTC](https://community.auth0.com/t/need-guidance-on-implementing-mfa-otp-via-auth0-api-for-post-login-transaction-verification/186937 "2025-05-20T07:28:08Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![exchanga](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/exchanga/32/65100_2.png) [@exchanga](https://community.auth0.com/u/exchanga)\
**Post date:** [May 20, 2025, 7:28am UTC](https://community.auth0.com/t/need-guidance-on-implementing-mfa-otp-via-auth0-api-for-post-login-transaction-verification/186937/1 "2025-05-20T07:28:08Z")

</div>

**Dear Auth0 Support Team,**

I have enabled **MFA with One-Time Password (OTP)** using the **“Always”** policy, which currently prompts users for QR code setup and OTP during login, working as expected.

However, my application requires an **additional MFA verification step during sensitive actions (e.g., completing a transaction)**  **after the user has already logged in**. I would like to trigger a second MFA OTP prompt via **Auth0 API** when such critical actions are performed inside the app.

I have reviewed the Auth0 documentation, but could not find a clear, end-to-end explanation or API-based flow that supports **on-demand or step-up MFA challenges after login**.

Could you please provide:

1. A brief explanation or best practice on how to implement **step-up authentication or additional MFA verification** after the user is logged in.
2. The **API endpoints** , configuration steps, and examples (if available) to trigger **MFA OTP manually** within the app during runtime.
3. Any **rules, actions, or policies** I should configure to support this use case.

I would appreciate your guidance on achieving this functionality.

---

<div class="post-metadata">

**Author:** ![teodor.andrei](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/teodor.andrei/32/75320_2.png) [@teodor.andrei](https://community.auth0.com/u/teodor.andrei)\
**Post date:** [May 20, 2025, 3:13pm UTC](https://community.auth0.com/t/need-guidance-on-implementing-mfa-otp-via-auth0-api-for-post-login-transaction-verification/186937/3 "2025-05-20T15:13:00Z")

</div>

Hi @exchanga, and thank you for your question!

Your use case is indeed intended to be solved with our Step-up Authentication feature. When your audience is an API, you can implement step-up authentication with Auth0 using [scopes](https://auth0.com/docs/get-started/apis/scopes), [access tokens](https://auth0.com/docs/secure/tokens/access-tokens), and [Actions](https://auth0.com/docs/customize/actions). You can use an Action to trigger the step-up authentication mechanism (for example, prompt MFA) whenever the user requests scopes that map to sensitive resources. For more information, please see our [docs](https://auth0.com/docs/secure/multi-factor-authentication/step-up-authentication#step-up-authentication-for-apis:~:text=mechanism%20like%20MFA.-,Step%2Dup%20Authentication%20for%20APIs,-When%20your%20audience). If this is the doc you mentioned reading, please check out our [configuration guide](https://auth0.com/docs/secure/multi-factor-authentication/step-up-authentication/configure-step-up-authentication-for-apis) for setting up the Step-up Authentication feature when the audience is an API.

I wish you a great day!

Sincerely,  
Teodor.

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/auth0/original/3X/b/5/b560f266932fcce5d57f09a6595bd50518cae3f3.jpeg) [@system](https://community.auth0.com/u/system)\
**Post date:** [June 3, 2025, 3:13pm UTC](https://community.auth0.com/t/need-guidance-on-implementing-mfa-otp-via-auth0-api-for-post-login-transaction-verification/186937/4 "2025-06-03T15:13:39Z")

</div>

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.
