Raiffeisenbank (Russia) · Authentication Profile

Raiffeisen Ru Authentication

Authentication

Raiffeisenbank (Russia) secures its APIs with apiKey and http across 4 declared security schemes, as derived from its OpenAPI definitions.

CompanyBankingFinancial ServicesCorporate BankingPaymentsOpen BankingRussia

Methods: apiKey, http Schemes: 4 OAuth flows: API key in: cookie

Security Schemes

bearerAuth http

scheme: bearer

UserTokenAuth apiKey

· in: cookie (X-USER-ACCESS-TOKEN)

oauth2-authorization-code (documented) oauth2

raif-pay-secretKey http

scheme: bearer

Source

Authentication Profile

generated: '2026-10-09'
method: searched
source: https://developer.raiffeisen.ru/docs/howToStart/tokens/howToGetTokensByCodeFlow; https://pay.raif.ru/doc/ecom.html; openapi/raiffeisen-ru-authorization-openapi.yml, openapi/raiffeisen-ru-raif-pay-corporate-cards-openapi.yml,
  openapi/raiffeisen-ru-raif-pay-payment-form-openapi.yml, openapi/raiffeisen-ru-raif-pay-payouts-openapi.yml, openapi/raiffeisen-ru-raif-pay-sbp-b2b-openapi.yml, openapi/raiffeisen-ru-raif-pay-sbp-b2b-transfers-openapi.yml,
  openapi/raiffeisen-ru-raif-pay-sbp-openapi.yml, openapi/raiffeisen-ru-raif-pay-whitelabel-ecom-openapi.yml
summary:
  types:
  - apiKey
  - http
  api_key_in:
  - cookie
schemes:
- name: bearerAuth
  type: http
  scheme: bearer
  bearerFormat: JWT
  description: Access Token, полученный в ответе /oauth2/token.
  sources:
  - openapi/raiffeisen-ru-authorization-openapi.yml
  - openapi/raiffeisen-ru-raif-pay-corporate-cards-openapi.yml
  - openapi/raiffeisen-ru-raif-pay-payment-form-openapi.yml
  - openapi/raiffeisen-ru-raif-pay-payouts-openapi.yml
  - openapi/raiffeisen-ru-raif-pay-sbp-b2b-openapi.yml
  - openapi/raiffeisen-ru-raif-pay-sbp-b2b-transfers-openapi.yml
  - openapi/raiffeisen-ru-raif-pay-sbp-openapi.yml
  - openapi/raiffeisen-ru-raif-pay-whitelabel-ecom-openapi.yml
- name: UserTokenAuth
  type: apiKey
  in: cookie
  parameter: X-USER-ACCESS-TOKEN
  sources:
  - openapi/raiffeisen-ru-raif-pay-payouts-openapi.yml
- name: oauth2-authorization-code (documented)
  type: oauth2
  flow: authorizationCode
  pkce: S256
  authorizationUrl: https://sso.rbo.raiffeisen.ru/authorize
  scopes:
  - openid
  - profile
  - email
  - phone
  description: 'Documented Code Flow: GET https://sso.rbo.raiffeisen.ru/authorize?scope=openid profile email phone&client_id=…&response_type=code&redirect_uri=…&state=…&nonce=…&prompt=login&code_challenge=…;
    /token uses HTTP Basic client_id:client_secret; access and ID tokens then sent as Authorization: Bearer plus ID-Token header; refresh via refresh_token. Prerequisites: be a bank client, submit and sign
    an integration application in the online bank. Tokens can alternatively be issued in the online bank.'
  source: https://developer.raiffeisen.ru/docs/howToStart/tokens/howToGetTokensByCodeFlow
- name: raif-pay-secretKey
  type: http
  scheme: bearer
  description: 'Raif Pay server-to-server requests: header Authorization = "Bearer " + secretKey; publicId is the public merchant identifier used to open the payment form. secretKey is generated in the
    online bank or merchant cabinet.'
  source: https://pay.raif.ru/doc/ecom.html
docs: https://developer.raiffeisen.ru/docs/howToStart/tokens/howToGetTokens
docs_pages:
- https://developer.raiffeisen.ru/docs/howToStart/tokens/howToGetTokens
- https://developer.raiffeisen.ru/docs/howToStart/tokens/howToGetTokensByCodeFlow
- https://developer.raiffeisen.ru/docs/howToStart/tokens/howToGetTokensInOnlineBank
- https://developer.raiffeisen.ru/docs/support
- https://pay.raif.ru/doc/ecom.html#section/Avtorizaciya

Work with this as data

Every security artifact here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for security posture

4 MCP tools reach this

find_securityBrowse and filter every security artifact in the catalog.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This security artifact

curl "https://apis.io/api/v1/security/raiffeisen-ru-authentication"

All security posture

curl "https://apis.io/api/v1/security?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.