CLIpayment
capxul payment send
you approve it in the browser
Runs in: devnet · staging · production · Moves money: yes
Usage
capxul payment send [flags] [<to>] [<amount>]Arguments
| Argument | Type | Required | Description |
|---|---|---|---|
<to> | string | no | who to pay: an email, a @handle or an 0x address |
<amount> | string | no | how much, like 50 or 12.5 |
Flags
| Flag | Type | Required | Description |
|---|---|---|---|
--asset | string | no | what to send: a symbol the payer holds |
--from | string | no | the Budget an Organization payment spends from: its name or ID |
--as-owners | boolean | no | pay from the Organization account itself; its Owners approve, no Budget |
--note | string | no | what an --as-owners payment is for, shown to the Owners |
--account | string | no | the account it is booked to: a code of your chart, like 6100 |
--suggest | string | no | a name for a new account, beside 4999 or 6999, for someone with Manage books |
--email | string | no | the signed-in person to use, when this machine has several |
--input | string | no | the SDK payment JSON, from a file or - for stdin |
--request-key | string | no | a key that makes repeating the same payment safe |
--timeout-seconds | integer | no | how long to follow it (default: until the approval lapses) |
Every command also takes the global flags.
Returns
The data of the result that --json prints:
--json: { status: 'awaiting_approval', approvalId, approvalUrl, paymentIds, expiresAt, next: { argv } }; a person, or --json replaying a request key whose approval was already answered: ApprovalOutcome { approval, payments }. It saves no PDF: `capxul document render` doesErrors
Generated from capxul schema payment send.