Step-up challenges

Send a push notification to step up a token

Starts step-up by sending a push notification to a device belonging to the logged-in user, as an alternative to the one-time password variant.

The channel is AUTHY or BIOMETRIC, and the device must have been enrolled beforehand through /authentication_factors/push/{channel}. The user approves the challenge on their device, so unlike the one-time password flow there is no code to collect and no verify call to make. The response returns the challenge id for correlating the notification you sent with the approval that follows.

Only start this if a step-up isn't already in flight for the token.

Once approved, the access token you are already using is raised to STEPPED_UP in place. Retry the operation that required step-up with the same token.

post/stepup/challenges/push/{channel}

Request

  • Base URL: https://sandbox.weavr.io/multi
  • URL: https://sandbox.weavr.io/multi/stepup/challenges/push/{channel}
  • Auth: HTTP bearer and API key in header api-key

Path parameters

channel'AUTHY' | 'BIOMETRIC' required
  • AUTHY: The push notification is sent on the user's device using Twilio Authy
  • BIOMETRIC: The push notification is sent to the user's device

The push channel used to deliver the SCA challenge.

Headers

idempotency-refstring
Example:transfer-2026-08-07-001

A unique call reference generated by the caller that, taking into consideration the payload as well as the operation itself, helps avoid duplicate operations. Idempotency reference uniqueness is maintained for at least 24 hours.

Response

Success

idstring

The challenge id.

Changes

No recorded changes to this operation across all 1 revision of this API.