/send

SynchronousAsynchronous

Update

This endpoint is fully functional; however, we recommend using the /send endpoint instead, as it offers greater flexibility. With the new /send, you can process multiple operators within the same request using the operatorId parameter.

Request Types

This endpoint supports both synchronous and asynchronous requests. You have the flexibility to choose between these two request types based on your preferences and requirements.

Synchronous Requests

If you prefer to receive an immediate response and want to wait for the transaction to be processed before proceeding, you should make a synchronous request. In this case, you do not need to include the useWebhook and webhookUrl parameters in the request body.

Asynchronous Requests

For those who wish to initiate a transaction and continue with their workflow without waiting for the processing to complete, asynchronous requests are the ideal choice. To make an asynchronous request, include the useWebhook and webhookUrl parameters in the request body. This allows the transaction to be processed in the background, and you will receive a webhook callback once it's confirmed.

Choose the request type that aligns with your use case to optimize your experience with this operator.

Request Code Samples

Shell

JavaScript

Java

Swift

PHP

Python

HTTP

Objective-C

Ruby

OCaml

Dart

Responses

🟢200ASYNC TRANSACTION

application/json

Body

Example

{
    "success": true,
    "message": "OK",
    "data": {
        "phoneNumber": "+584161234567",
        "amount": "75",
        "hash": "2deb110b57bfac9d72c14d4ed9622222",
        "transactionId": "1b3df83e100d341533f0db1a5bbbc584",
        "operator": "MOVILNET PREPAID",
        "operatorReference": null,
        "status": "PENDING",
        "useWebhook": true,
        "webhookUrl": "https://mywebhookurl.mydomain/myendpoint"
    }
}

Update#

Request Types#

Synchronous Requests#