With this service, the calling apps can instruct a provider via OnePipe to validate an OTP supplied by a customer. The added benefit here is that in the event that a provider needs authorization details of the account to debit for the value of the SMS or whatever the transport protocol is (bank account, wallet, etc) this can be supplied to the provider.
| Info |
|---|
Before you proceed: Please read this. |
...
| Gliffy |
|---|
| imageAttachmentId | att256213224 |
|---|
| macroId | 58548c81-952b-44cf-bc6d-ac9cee86621a |
|---|
| baseUrl | https://onepipe.atlassian.net/wiki | macroId | 58548c81-952b-44cf-bc6d-ac9cee86621a |
|---|
| name | OnePipe 2.0 - Service - No OTP |
|---|
| diagramAttachmentId | att255951120 |
|---|
| containerId | 256147586 |
|---|
| timestamp | 1585104185283 |
|---|
|
...
| Code Block |
|---|
|
{
"request_ref":"{{request_ref}}",
"request_type":"validate_otp",
"auth": {
"type": "bank.account | card | wallet | msisdn",
"secure": "{{encrypted(bank account number | card details | wallet | msisdn)}}", //if payment should be collected realtime, it would be charged here
"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": {
"reference": "1234567890",
"otp": "123456"
}
}
} |
...
| Code Block |
|---|
|
{
"status": "Successful",
"message": "TransactionOTP processedvalidated successfullycorrectly",
"data": {
"provider_response_code": "00",
"provider": "Beeceptor",
"errors": null,
"error": null,
"provider_response": {
"cost": "1200",
"reference": "50617644717007000022200225154318222333334432",
"costmeta": "1200"{
"field_key":"field_value",
"field_key":"field_value"
}
}
}
} |
Breakdown of the details object
...