...
| Code Block | ||
|---|---|---|
| ||
{
"request_ref":"{{request_ref}}",
"request_type":"lookup_bvn_2",
"auth": {
"type": null,
"secure": null,
"auth_provider": "Beeceptor",
"route_mode":"null"
},
"transaction": {
"mock_mode": "live",
"transaction_ref": "{{transaction_ref}}",
"transaction_desc": "A random transaction",
"transaction_ref_parent": null,
"amount": 0,
"customer":{
"customer_ref": "{{customer_id}}",
"firstname": "Uju",
"surname": "Usmanu",
"email": "ujuusmanu@gmail.com",
"mobile_no": "234802343132"
},
"meta":{
"a_key":"a_meta_value_1",
"another_key":"a_meta_value_2"
},
"details": {
"account_numberbvn":"23632626327",
"otp_override": true
}
}
} |
...
Special notes for OTP override
Provider microservice should always store retrieved Whenever a request is to be validated by OTP, the provider microservice should first call the provider, store response info in the database if request is to be validated with OTP. , then respond with WaitingForOTP.
On the OTP validation leg, if user OTP is valid, provider should retrieve info from the database, then forward to the calling apprespond with a Successful response.
NB: Data should be erased from the DB.
Special notes for providers
...