Rumba Pay
  • Welcome
  • Getting Started
    • Authentication
    • Signature
  • Payment methods
    • Argentina
      • Bank transfer Argentina
        • Payment
        • Payout
    • Brazil
      • PIX
        • Payment
        • Payout
    • Chile
      • Cash
        • Payment
      • Bank transfer Chile
        • Payment
        • Payout
  • Mexico
    • Cash
      • Payment
    • Bank transfer Mexico
      • Payment
      • Payout
  • Ukraine
    • P2C
      • Payment
    • Card
      • Payout
  • Kazakhstan
    • P2C
      • Payment
    • Card
      • Payout
  • Kyrgyzstan
    • P2C
      • Payment
    • Card
      • Payout
  • Uzbekistan
    • P2C
      • Payment
    • Card
      • Payout
Powered by GitBook
On this page
  • Overview
  • Callback
  • Check Payout Status
  1. Payment methods
  2. Argentina
  3. Bank transfer Argentina

Payout

Overview

The Rumbapay Payout API allows you to make payouts to your clients' bank accounts. This document provides instructions on how to create and manage bank transfer payouts.

How exactly Bank Transfer Payout works:

  1. Merchant makes a request to create a bank transfer payout;

  2. Rumbapay processes the payout, interacting with the appropriate banking provider;

  3. Rumbapay sends a webhook to the merchant once the transaction status becomes terminal.

Base URL:

  • https://api.rumbapay.online/v1/

Data Format: JSON

HTTP Methods: POST, GET


Initialize Payout

Method: HTTP POST

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

Request Body:

{
    "method": "bank_transfer_argentina",
    "reference": "order-00001", // required
    "currency": "ARS", // required
    "amount": 25.01, // required
    "description": "My order payout", // optional,
    "customer":// required
    { 
        "identifier": "1111-1111-2211-2211", // required, any unique value from the merchant's system may be used.
        "email": "juancarlos@hotmail.com", // optional
        "phone": "+5491123456789", // optional
        "first_name": "Juan", // required
        "last_name": "García Rodríguez", // required
        "middle_name": "Carlos", // optional
        "country": "AR",  // optional, Argentina (ISO 3166-1 country code for Argentina)
        "state_code": "B",  // optional, Buenos Aires Province (ISO 3166-2 state code for Buenos Aires)
        "city": "Buenos Aires", // optional
        "address": "Calle Emilio Mitre 3256", // optional
        "zip_code": "C1407", // optional
        "itn": "X1234567890",  // required, CUIT/CUIL/CDI number (Argentine tax identification number) 
        "birthday": "2006-01-02", // optional
        "ip": "192.168.0.1", // optional
        "gender": "male" // optional
    },
    "requisites": { // required
        "account_number": "1000296999931", // required
        "account_number_alias": "For testing", // optional
        "beneficiary_first_name": "Darth", // required
        "beneficiary_last_name": "Veider", // required
        "beneficiary_email": "test@gmail.com", // optional
        "beneficiary_phone": "5491123456789", // optional
        "beneficiary_document_type": "cuit", // optional, possible values: "cuit", "cuil" or "cdi"
        "beneficiary_document_value": "20123456789"// required
    },
    "lang":"es",// optional
    "redirect_url": "redirect_url", // optional
    "cancel_url": "cancel_url", // optional
    "callback_url": "callback_url", // conditional
    "extra":  // any field which may be needed for transaction routing and integration
    [
        {"key_1":"value"},
        {"key_2":"value"}
    ]
}

Response (Success):

{
    "identifier": "BAN000118362",
    "request_id": "15195dfe-95dd-4916-95e2-b9696cff61ba",
    "reference": "334545",
    "description": "My order h2h",
    "status": {
        "name": "pending",
        "date": "2025-05-05T18:51:38.266"
    },
    "created_date": "2025-05-05T18:51:38.265",
    "amount": 14,
    "billing_amount": 0,
    "currency": "ARS",
    "requisites": {
        "account_number": "1000296999931",
        "account_number_alias": "For testing",
        "beneficiary_last_name": "Veider",
        "beneficiary_email": "test@gmail.com",
        "beneficiary_phone": "5491123456789",
        "beneficiary_document_type": "cuit",
        "beneficiary_document_value": "20123456789"
    },
    "extra": [
        {
            "key": "key_2",
            "value": "value"
        },
        {
            "key": "key_3",
            "value": "value"
        },
        {
            "key": "key_4",
            "value": "value"
        },
        {
            "key": "key_1",
            "value": "value"
        }
    ],
    "timestamp": "2025-05-05T18:51:44.3527856Z",
    "error_code": 0,
    "error_message": "success"
}

Response - 400 Bad request

{
    "error_code": 30,
    "error_reason": "Invalid params",
    "request_id": "15195dfe-95dd-4916-95e2-b9696cff61ba",
    "error_fields": [
        {
            "field": "account_number",
            "message": "account_number is a required field"
        }
    ],
    "timestamp": "2025-04-11T16:58:57.11Z"
}

Callback

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

Callback flow

The callback flow follows these steps:

  1. Rumbapay processes the payout request

  2. When the payout 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

Example

{
  "error_code": 0,
  "error_message": "success",
  "identifier": "BAN000096257",
  "request_id": "861bc24d-468a-41ae-b8fd-53945301c738",
  "reference": "334545",
  "description": "My order h2h",
  "status": {
    "name": "pending",
    "date": "2025-04-24T10:53:50.873"
  },
  "created_date": "2025-04-24T10:53:41.78",
  "amount": 33333,
  "billing_amount": 33333.74,
  "currency": "ARS",
  "requisites": {
        "account_number": "1000296999931",
        "account_number_alias": "For testing",
        "beneficiary_first_name": "Darth",
        "beneficiary_last_name": "Veider",
        "beneficiary_email": "test@gmail.com",
        "beneficiary_phone": "5491123456789",
        "beneficiary_document_type": "cuit",
        "beneficiary_document_value": "20123456789"
  },
  "extra": [
    {
      "key": "key_4",
      "value": "value"
    },
    {
      "key": "key_3",
      "value": "value"
    },
    {
      "key": "key_2",
      "value": "value"
    },
    {
      "key": "key_1",
      "value": "value"
    }
  ],
  "timestamp": "2025-04-24T07:53:55.0041761Z"
}

Check Payout Status

Method: HTTP GET

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

Response (Success):

{
    "error_code": 0,
    "error_message": "success",
    "identifier": "BAN000096257",
    "request_id": "861bc24d-468a-41ae-b8fd-53945301c738",
    "reference": "334545",
    "description": "My order h2h",
    "status": {
        "name": "pending",
        "date": "2025-04-24T10:53:50.873"
    },
    "created_date": "2025-04-24T10:53:41.78",
    "amount": 33333,
    "billing_amount": 33333.74,
    "currency": "ARS",
    "requisites": {
        "account_number": "1000296999931",
        "account_number_alias": "For testing",
        "beneficiary_first_name": "Darth",
        "beneficiary_last_name": "Veider",
        "beneficiary_email": "test@gmail.com",
        "beneficiary_phone": "5491123456789",
        "beneficiary_document_type": "cuit",
        "beneficiary_document_value": "20123456789"
    },
    "extra": [
        {
            "key": "key_4",
            "value": "value"
        },
        {
            "key": "key_3",
            "value": "value"
        },
        {
            "key": "key_2",
            "value": "value"
        },
        {
            "key": "key_1",
            "value": "value"
        }
    ],
    "timestamp": "2025-04-24T07:56:56.4542318Z"
}

Response (Not Found):

Transaction not found

{
    "error_code": 101,
    "error_reason": "Transaction not found",
    "request_id": "b6ed6ffe-0a62-480c-92fb-a84558a2da53",
    "timestamp": "2025-04-11T16:58:57.11Z"
}
PreviousPaymentNextBrazil

Last updated 1 month ago

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

signature