Verify Receiver Registration

POST 
/wallet-registration/verification

This endpoint verifies the receiver's registration by validating the OTP and other verification values provided in the request body. A valid SEP-24 token should be included in the Authorization header of the request.

Request

Header Parameters

Authorization stringrequired

SEP-24 token for authorization (Format: 'Bearer {token}')

application/json

Body

required

Verification data including phone_number/email, OTP, verification value, and reCAPTCHA token

email string

Email associated with the receiver in the SDP database. Either phone_number or email is required.

phone_number string

Phone number associated with the receiver in the SDP database. Either phone_number or email is required.

otp string

One-Time Password received for verification

verification string

Verification value provided by the user

verification_field VerificationField (string)

Possible values: [DATE_OF_BIRTH, YEAR_MONTH, PIN, NATIONAL_ID_NUMBER]

recaptcha_token string

Token received from Google reCAPTCHA

Responses

200

Verification successful

application/json

Schema

Schema

message string

Example (from schema)

{
  "message": "ok"
}

400

Bad Request

application/json

Schema

Schema

error string

Details about the error

extras

object

object

Example (from schema)

{
  "error": "Invalid input",
  "extras": {
    "field_foo": "field_foo is required",
    "field_bar": "field_bar needs to be an integer"
  }
}

401

Unauthorized

application/json

Schema

Schema

error string

extras

object

status number

message string

Example (from schema)

{
  "error": "Not authorized",
  "extras": {
    "status": 401,
    "message": "Not authorized"
  }
}

Example

{
  "error": "Not authorized",
  "extras": {
    "status": 401,
    "message": "Not authorized"
  }
}

Loading...