> For the complete documentation index, see [llms.txt](https://ninjapay.gitbook.io/ninjapay-api-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ninjapay.gitbook.io/ninjapay-api-docs/coming-soon/api-reference-pro/send-payment.md).

# Send Payment

Request to sends a payment from a wallet. The application needs to provide an lightning invoice or Ninjapay username(@ninjatag) or on-chain address . We recommend using **ninjatag**(Ninjapay username) for sending rewards to users, since it's zero fee and instant. 

#### **Method**

```

POST https://prod.ninjapay.me/sapi/v1/send

```

#### **Parameters**

```javascript
Body (application/json)
 {
  wallet: string; // lbtc, btc and usdt supported currently
  payment_mode: string; // ninjatag, onchain, lightning
  ninjatag?: string; // Add this username if you want to send to other ninjapay users
  lightning_invoice?: string; // Add this if you want to send payment via lightning
  lightning_invoice_type?: string; // "invoice"(default) and "lnurl" currently supported(lnurl not supported for "btc" wallet)
  chain_address?: string; // Add this if you want to send payment onchain
  chain_network?: string; // Add network for onchain payment (BTC, ERC20, BEP20...)
  amount?: int; // For both "btc" & "lbtc" wallets, amount should be entered in BTC, not SAT. (Amount is not required for "lbtc" unless lightning_invoice_type is "lnurl")
  fiat_value?: int;
  fiat_currency?: string; // INR, USD, EUR...
  description?: string;
  customer_name?: string;
  order_id?: string;
  extra?: {}
}
```

#### **Other info**

| Parameters      | Input options                                |
| --------------- | -------------------------------------------- |
| `wallet`        | `lbtc`,`btc`,`usdt`                          |
| `payment_mode`  | `ninjatag` , `onchain`, `lightning`, `email` |
| `chain_network` | `BTC` , `ERC20`, `BEP20`, `MATIC`            |

#### **Response**

```json
{"tid": <int>}
```

#### **Example**

{% code overflow="wrap" %}

```javascript

const options = {
  method: 'POST',
  headers: {
    'Content-Type': 'application/json',
    Authorization: 'API_KEY'
  },
  body: '{"wallet":"lbtc","payment_mode":"ninjatag","amount":0.0018,"description":"sample_description","ninjatag":"nakamoto","order_id":"21"}'
};

fetch('https://prod.ninjapay.me/sapi/v1/send', options)
  .then(response => response.json())
  .then(response => console.log(response))
  .catch(err => console.error(err));
  
  
```

{% endcode %}

**Note:** You need to use `Admin key` for this request!


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://ninjapay.gitbook.io/ninjapay-api-docs/coming-soon/api-reference-pro/send-payment.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.