Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. App calls /transact with the right auth details (if supplied)

  2. Provider responds with WaitingForOTP or PendingValidation (if required)

  3. App calls /transact/validate to supply OTP if needed

  4. Provider responds with any of the completion codes Successful or Failed.

  5. To query the status of a transaction, the app can call /transact/query

  6. Where the provider supports it, the app can call /transact/reverse to request a reversal

Gliffy
imageAttachmentIdatt214040634
baseUrlhttps://onepipe.atlassian.net/wiki
macroId5c111e2f-045e-4c81-9b69-ca5cb8264163
nameOpen Account
diagramAttachmentIdatt204964130
containerId214007878
timestamp1583764581910

INTERFACE SPECIFICATION (APP → ONEPIPE)

...

Code Block
languagejson
{
    "status": "Successful",
    "message": "Transaction processed successfully",
    "data": {
        "provider_response_code": "00",
        "provider": "Beeceptor",
        "errors": null,
        "error": null,
        "provider_response": {
            "referencenew_pin": "22333055551234",
            "new_pinpin_offset": "1245",
            "reference": "1234000022200225154318222333334432",
            "pin_offset": "1245"meta":{
              "field_key":"field_value",
              "field_key":"field_value"
            }
        }
    }
}

Request (validate with otp)

...