BetaTransfer
    • Guide of Integration
    • Signature generation
    • CMS Modules for Payment Integration
    • Payment & Withdrawal Statuses
    • Refill
      • Payment
        POST
    • H2H
      • Step 1. Initialization
        POST
      • Step 2. Payer card data
        POST
    • Withdrawal
      • Reference: Bank Codes for SBP Integrations
      • Creating a withdrawal request
        POST
    • Information methods
      • Info
        POST
      • Obtaining transaction history
        POST
      • Account balance and status information
        GET
      • Information about available methods, fees, limits, etc.
        GET
    • Webhooks
      • On Withdrawal Status Change
      • On Payment Status Change
    • Schemas
      • Response
        • PayinCreate
        • ValidationError
        • PayinView
        • BadRequest
        • Forbidden
        • NotFound
    • Schemas
      • Response
      • RequestBodies
      • Schemas

    Guide of Integration

    🚀 Quick Start: How to integrate#

    1. Get your API credentials#

    You will receive an API key and an API secret from your account manager / partner portal.
    Keep the secret key safe — it will be used to sign all requests.

    2. What to send: building a request#

    For each request to the API, you must include a valid signature. The signature ensures data integrity and authenticates your request.
    To build the signature see Signature generation
    Add the resulting signature into the request body as specified by the API.

    3. Sample request (in different languages)#

    Provide example requests to make integration easier. For example, in PHP, Python, Node.js, etc. — showing how to build the signature and how to send the request correctly. (On your documentation site, you already have sample snippets for several languages.)
    BetaTransfer

    4. Available endpoints & workflows#

    All API endpoints are organized into logical groups:
    Payment
    Create Payment (POST)
    H2H
    Step 1: Initialization (POST)
    Step 2: Payer Card Data (POST)
    Withdrawal
    Create Withdrawal Request (POST)
    Information
    Transaction / Payment Info (POST)
    Callbacks / Webhooks
    Status updates sent to your system
    Each endpoint describes:
    what scenario it belongs to
    required and optional fields
    signature rules
    example requests & responses
    This structure makes it easy to understand which endpoint corresponds to which business use-case (web payment, H2H payment, withdrawal processing, info queries, etc.).

    5. What to expect: responses & error handling#

    All endpoints return structured responses:
    200 OK — success
    400 Bad Request — validation errors
    403 Forbidden — incorrect signature or no access
    404 Not Found — object not found
    422 Unprocessable Entity — invalid format / failed schema validation
    Schemas and response examples are available on each endpoint page.
    Your integration should:
    parse responses
    handle error statuses
    log error messages and codes
    fail gracefully on invalid or missing parameters

    6. CMS Modules for Payment Integration#

    For quick and seamless integration, BetaTransfer provides ready-made modules for popular CMS platforms.
    👉 CMS Modules for Payment Integration
    These modules let merchants integrate payments without writing the integration from scratch.
    The page includes:
    list of supported CMS systems
    module installation guides
    configuration instructions
    callback URL setup
    common troubleshooting tips
    If your merchant uses one of the supported platforms, installing the CMS module is the fastest way to start accepting payments.

    7. Further reading / detailed reference#

    Once the quick-start is complete, developers can navigate to deeper documentation pages:
    Full list of endpoints, with details of request/response bodies and parameters.
    Schema reference (requests and responses).
    Webhook specification (for payment status changes, withdrawal status, etc.).
    Code samples in various languages.
    Integration scenarios / flow diagrams (e.g. typical payment flow, H2H flow, withdrawal flow).
    Modified at 2026-02-23 15:11:40
    Next
    Signature generation
    Built with