Events and errors

What the SDK tells your app as a journey or call goes on, and why it may not start.

Events

Events carry identifiers only. Nothing the customer types or photographs ever reaches your app: it goes to your institution.

EventWhenData
journey.startedThe journey's first page is showingpageId
journey.page_changedThe customer reached another pagepageId
journey.submittedThe application was submittedreference — what the customer quotes
journey.blockedYour institution takes no further application from this customer now—
vkyc.joinedThe customer joined their video call—
vkyc.endedThe video call is over—

On Android compare `event.type` with the `PayMediaEvent.Type` constants; on iOS use `event.kind`. Your listener's `onClosed`, or your delegate's `payMediaDidClose`, is called whenever the customer leaves the SDK's screen.

Errors

The SDK shows no error screen of its own for these. Your app decides what to tell the customer.

CodeMeaningWhat to do
NETWORKThe journey host could not be reachedOffer to try again
SDK_KEY_INVALIDThe key is unknown, revoked or for another institutionCheck the key in your build; create a new one in Institution Admin
SDK_APP_NOT_ALLOWEDThis app is not on the environment's allowed listAllow the app, or check the signing certificate's SHA-256
SDK_DISABLEDNew journeys are paused by the kill switchTell the customer onboarding in the app is unavailable for now
SDK_VERSION_UNSUPPORTEDThis SDK version is older than you acceptAsk the customer to update the app, or open the web journey it carries
CONFIGURATIONThe SDK was not configured, or a link is not on your journey hostFix the integration
UNSUPPORTEDThe phone's system software is too old to run the journey securely (Android)Ask the customer to update their phone's software
INTERNALSomething unexpectedLog it and offer to try again