search

Payment

Overview

Rumbapay provides two options for processing payment requests: redirection to the Rumbapay payment page (HPP) and direct server-to-server communication (H2H). When creating a payment using the method https://api.rumbapay.online/v1/payment you must inspect the challenge.challenge_type field to determine the appropriate flow.

Base URLs: https://api.rumbapay.online/v1/

Data Format: JSON

HTTP Methods: POST, PUT, GET

hashtag
Initialize payment

When creating a payment using the method https://api.rumbapay.online/v1/payment you must inspect the challenge.challenge_type field to determine the appropriate flow.

Method: HTTP POST

URL: https://api.rumbapay.online/v1/payment

circle-check

Initialize Payment request (request body) can take two forms: Type 1 and Type 2

The system accepts and processes both types of requests. Requests are handled identically, regardless of the request body format.

Request Body Type H2H:

{
    "method": "e_wallet", // required
    "mode": "initial", // required, only "initial" for this method
    "reference": "334545", // required
    "currency": "BOB", // required
    "amount": 25.01, // required
    "description": "My order h2h", // optional
    "customer":// required
    {
        "identifier": "1111-1111-2211-2211", // required, any unique value from the merchant's system may be used.
        "email": "joaosilva@hotmail.com", // optional
        "phone": "+573190437224", // required, 6-20 digits
        "first_name": "João", // required
        "last_name": "Silva", // required
        "middle_name": "Pereira", // optional
        "country": "BO",  // optional, Bolivia(ISO 3166-1 country code for Bolivia)
        "state_code": "SP",  // optional, São Paulo (ISO 3166-2 state code for São Paulo)
        "city": "São Paulo", // optional
        "address": "Avenida Paulista 1578", // optional
        "zip_code": "01310-200", // optional
        "itn": "65745728000",  // required,
        "birthday": "1985-04-12", // optional
        "ip": "192.168.0.1", // required
        "gender": "male" // optional
    },
    "redirect_url": "redirect_url", // optional
    "cancel_url": "cancel_url", // optional
    "callback_url": "callback_url", // conditional
    "extra":  // conditional, any field which may be needed for transaction routing and integration
    [{"key_1":"value"},{"key_2":"value"},{"key_3":"value"},{"key_4":"value"}]
}

Request Body Type HPP:

circle-info

💡The payment process depends on challenge_type parameter received

  1. Merchant sends a payment request to https://api.rumbapay.online/v1/payment

  2. Rumbapay validates the request and returns payment details including:

    • A single EMV-compliant text string that encodes every piece of information needed for the E-Wallet QR code. Under the hood it's a series of "tag–length–value" segments (two-digit tags, two-digit lengths, then the data), which together tell a scanner exactly how to process the payment.

    • A URL pointing to your server's QR-code generator. When you pass the code string to this endpoint, it returns a visual QR image (PNG, SVG, etc.) that users can scan to complete the E-Wallet payment.

  3. Rumbapay or provider processes the submission and updates the payment status to "pending"

  4. Customer makes the payment using their banking app by scanning the QR code or clicking the payment link, which opens the bank's app or website where they review the details and confirm the transaction.

  5. Rumbapay verifies the payment with the banking provider

  6. Rumbapay sends a callback to the merchant's callback URL when the payment reaches a terminal state (success, error, etc.)

  1. Merchant sends a payment registration request to https://api.rumbapay.online/v1/payment

  2. Rumbapay validates the request and returns a redirect_url for the customer

  3. Merchant redirects the customer to the provided redirect_url, where a payment form will be displayed

  4. Rumbapay or provider processes the submission and updates the payment status to "pending"

  5. Customer makes the payment using their banking app by scanning the QR code or clicking the payment link, which opens the bank's app or website where they review the details and confirm the transaction.

  6. If a redirect_url was specified in the initial registration request, Rumbapay redirects the customer to that URL; otherwise, Rumbapay displays its own status page to the customer

  7. Rumbapay verifies the payment with the banking provider

  8. Rumbapay sends a callback to the merchant's callback URL when the payment reaches a terminal state (success, error, etc.)

  9. Additionally, the merchant can check the payment status at any time by sending a request to https://api.rumbapay.online/v1/transaction/{request_id} as described in the "Check Payment Status" section

Response (Success):

Response - 200 OK

  1. First, you should check error_code field of response.

    If error_code field is not equals to 0 - transaction is Failed.

  2. Second, you should check status field.

    The status field will always be set to created if there are no errors.

    Make check request or wait for a callback to get final transaction status.

hashtag
Challenge type: redirect

circle-info

If the challenge.challenge_type is set to redirect, you must send your Customer to the URL specified in challenge.challenge_redirect.url.

hashtag
Challenge type: QR

If the challenge.challenge_type is QR, prompt the user to make a payment using challenge.challenge_qr.code link or scan QR code that is built using code in challenge.challenge_qr.code

Customer makes the payment using their banking app by scanning the QR code or clicking the payment link, which opens the bank's app or website where they review the details and confirm the transaction.

Rumbapay sends a callback to the merchant's callback URL when the payment reaches a terminal state (success, error, etc.)

hashtag
Response - 400 Bad request

hashtag
Callback

On every completed Payout we send a callback notification to the URL you passed in the request in the callback_url field.

circle-exclamation

We strongly recommend validating the callback signature to avoid suspicious activity. Follow the signature docs to prepare callback verification.

hashtag
Callback flow

The callback flow follows these steps:

  1. Rumbapay processes the payment request

  2. When the payment status changes to a terminal state, Rumbapay sends an HTTP POST request to your callback URL

  3. Your server should process the callback, validate the signature, and update your system

  4. Your server should respond with HTTP 200 OK to acknowledge receipt

hashtag
Example

hashtag
Check Payment Status

Method: HTTP GET

URL: https://api.rumbapay.online/v1/transaction/{request_id}

Response (Success):

hashtag
Response (Not Found):

Transaction not found

PreviousE-WalletNextBank transfer Bolivia

Last updated