---
title: "Send payment"
method: POST
path: "/accounts/{account_id}/payments"
tags: ["Minimum"]
---

# Send payment

`POST /accounts/{account_id}/payments`

## Path parameters

- `account_id` string, required

## Request body

- Payment
  - `id` string, required
  - `account_id` string, required
  - `currency` 'XUS' | 'XDX', required
  - `amount` integer, required
  - `payee` string, required — The receiver address of the payment. Only support account identifier defined in DIP-5 for now. We will add Diem ID support in the future when the protocol related is stabilized.

## Response `202`

The server accepts the payment request. 
* The server may reflect the payment sent in the account balance immediately. 
  The funds being sent are considered to be in the process of being transferred 
  out and should not be used for any other purpose. 
* Once a client receives the response, expect the payment to be sent in a short time. 
  But it is not a limit to the server to complete the payment before respond the request.
* Client can confirm if the payment is completed by:
    * Checking if the sending and receiving account balances have been updated accordingly. 
    * Checking if the sending or receiving wallet app exposes an event using the get account events endpoint. 
* The optional get account events endpoint (if implemented) can be used to confirm if the action has failed.

- ResourceID
  - `id` string, required — ID of the resource created.

## Other responses

- `400` — Invalid input

---

[API](https://skmtc.net/diem/apis/mini-wallet-api-specification.md) · [All operations](https://skmtc.net/diem/apis/mini-wallet-api-specification/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/diem/mini-wallet-api-specification/versions/b3821c80b8b2/schema)