# Verifications (OTP)

**OTP Verification** - Email verification using one-time password (OTP) codes.
**Key Operations**:
- Request OTP code to be sent to customer's email
- Verify OTP code to confirm email ownership

**Flow**:
1. Request OTP via `POST /eapi/v0/verifications/otp`
2. Customer receives OTP code via email
3. Verify OTP via `POST /eapi/v0/verifications/otp/verify`

**Rate Limits**:
- OTP requests: 3 per minute per customer
- OTP verification attempts: 4 per minute per customer

**Important Notes**:
- OTP codes are single-use and expire after a set time
- Email must be verified for certain compliance requirements
- Feature must be enabled for your merchant account

 - [POST /eapi/v0/verifications/otp](https://docs.banxa.com/products/native-api/openapi/verifications/requestotp.md): Sends a one-time password (OTP) code to the customer's email address for verification. The OTP code is valid for a limited time and can only be used once. Rate limited to 3 requests per minute per cus
 - [POST /eapi/v0/verifications/otp/verify](https://docs.banxa.com/products/native-api/openapi/verifications/verifyotp.md): Verifies the OTP code sent to the customer's email address. Upon successful verification, the customer's email is marked as verified. OTP codes are single-use and expire after a set time period. Rate