# Step-up Authentication using Push Notifications
{% hint style="warning" %}
Onboarding for CIBA is only for Government agencies and on a case-by-case basis.
{% endhint %}
## Introduction
This guide illustrates the Step-up Authentication (Push Notifications) Flow and the APIs that Relying Parties (RP) need to integrate with.
The Step-up authentication feature can be employed in use-cases where RPs require their users to perform an additional layer of authentication before proceeding on with a **high-risk transaction**. This kind of authentication is done by triggering a push notification to the user’s Singpass Mobile Application.
RPs who are looking to opt-in for Step-up Authentication are required to integrate with Singpass operating in the **Client-initiated Backchannel Authentication (CIBA) Poll Mode** (see [CIBA specs](https://openid.net/specs/openid-client-initiated-backchannel-authentication-core-1_0.html#rfc.section.7)). Refer to this diagram for an overview of the CIBA authentication flow between an RP, Singpass and its dependencies.
CIBA Authentication Flow between RP, Singpass and its dependencies
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://docs.developer.singpass.gov.sg/docs/client-initiated-backchannel-authentication-ciba/step-up-authentication-using-push-notifications.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.