capxul bank pay
Pay a bank account; approve in your browser
Runs in: devnet · staging · production · Moves money: yes
Usage
capxul bank pay [flags] [<self|contact>] [<amount>] [<unit>]Arguments
| Argument | Type | Required | Description |
| ---------- | --------- | -------- | ------------------------------------------------------- | ------------------------------------------ |
| <self | contact> | string | no | whose bank to pay: self or a saved contact |
| <amount> | string | no | how much reaches the bank, unless an asset unit follows |
| <unit> | string | no | USDC or EURC to fix the source amount instead |
Flags
| Flag | Type | Required | Description |
|---|---|---|---|
--account | string | no | the saved bank account ID |
--asset | string | no | the funding asset: USDC or EURC |
--from | string | no | the Organization Budget name or ID |
--input | string | no | payout JSON file, or - for stdin |
--request-key | string | no | reuse this key when retrying the same payout |
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 }, quote, warnings }; a person, or --json replaying a request key whose approval was already answered: ApprovalOutcome { approval, payments }, with quote and warnings; signed but still in transit at the deadline: { status: 'in_transit', approvalId, paymentIds, next: { argv }, quote, warnings }. Each also carries stage, stageReason?. stage: 'quoted' | 'funding' | 'in_transit' | 'delivered' | 'needs_attention', or a later word shown as it is; stageReason: why a person looks, with needs_attention. quote: { receive, send, slippage?, rate?, expiresAt }; warnings: { code, message, next? }[]. It saves no PDF: `capxul document render` doesErrors
Generated from capxul schema bank pay.