Skip to main content
POST
Verify OTP
This is step 2 of the OTP-verified collection flow. Step 1 is the standard Unified Collections request, which returns a payment_token instead of a terminal status when OTP verification is required. See the OTP-Verified Payins guide for the full walkthrough.

Body

application/json

Signed request envelope carrying the OTP and payment token from step 1.

client_id
string
required

Your Client ID from the Niobi Dashboard under Workspace > Integrations.

sender
string
required

The exact title of your integration as registered in the Dashboard. Case-sensitive.

timestamp
integer
required

Unix timestamp in seconds at the time of signing. Must match the value used to generate the signature.

salt
string
required

A unique random string you generate per request. Must be the same value used when generating the signature.

signature
string
required

SHA-256 signature computed from this payload. Generate via the Signature endpoint or your own backend.

params
object
required

Response

Success

success
boolean
Example:

true

message
string
Example:

"Transaction completed successfully."

data
object