Raiffeisenbank (Russia) Payout Controller API

openapi: 3.2.0
info:
  title: Raiffeisen Ru Payout Controller API
  version: '1.0'
  contact:
    email: ecom@raiffeisen.ru
    name: Support e-mail
    x-team-id: 933
    x-short-team-name: PPO
  x-description-i18n:
    eng: 'You can give your comments about current documentation in repository: https://github.com/Raiffeisen-DGTL/ecom-API/blob/master/payout.yaml


      # API Description

      The interaction is carried out via the HTTP protocol using the GET / POST methods (the required method and address are clearly indicated in the description of each request).


      POST requests use JSON arguments, GET requests work with query strings.


      The API always returns a response in JSON format, regardless of the type of request.


      The standard response of the service contains a message code (code).

      If a logical error occurs during request processing, the API will additionally return a description of the error (message).


      # Workflow scheme

      ## One step processing

      Upon receipt of a request for payment, the bank immediately conducts all checks and, if the operation can be carried out, makes the payment.


      <a href=''images/one-step_payout_en.png'' target=''_blank''><img src=''images/one-step_payout_en.png''/></a>


      ## Two-stage processing

      With two-stage processing, a payout request is created, the bank checks the possibility of such an operation and returns the result. Further confirmation of the payout from the partner is expected.

      This interaction scheme is suitable when it is required to separate the creation of an application and its approval.

      Example: the manager creates a payout request, the manager or chief accountant confirms the payout.


      <a href=''images/two-step_payout_en.png'' target=''_blank''><img src=''images/two-step_payout_en.png''/></a>


      # Authorization

      Authorization is performed using a secret API key (secretKey). The authorization parameter is specified in the Authorization header, the value of which is formed as "Bearer secretKey".


      The list of IPs from which the system will pass requests is also configured.'
  x-logo:
    url: images/raifflogo.png
    backgroundColor: '#FFFFFF'
    altText: Raiff logo
  description: 'Operations tagged payout-controller across 2 of this provider''s published API definitions: raiffeisen-ru-raif-pay-payouts-openapi.json, raiffeisen-ru-raif-pay-payouts-openapi.yml. Each path carries the servers of the definition it was published in.'
servers:
- url: https://pay-test.raif.ru/api
  description: Sandbox
- url: https://pay.raif.ru/api
  description: prod
tags:


# --- truncated at 32 KB (195 KB total) ---
# Full source: https://raw.githubusercontent.com/api-evangelist/raiffeisen-ru/refs/heads/main/openapi/raiffeisen-ru-payout-controller-api-openapi.yml