Host your own payouts facilitator

NET=mainnet                                   # devnet | testnet | mainnet
NAME=acme-payouts                             # the Worker name: also its database and cache
ORG=did:ixo:entity:<your company entity>
SESSION=~/.ixo/publish-session-$NET.json

npx --yes @ixo/payouts-facilitator@0.2.0 deploy --network $NET --name $NAME --entity $ORG --rails stripe

STRIPE_SECRET_KEY="$(pbpaste)" npx --yes @ixo/payouts-facilitator@0.2.0 deploy \
  --network $NET --name $NAME --entity $ORG --rails stripe --stripe-webhook --yes --json
pbcopy < /dev/null    # clear the clipboard

npx --yes @ixo/payouts-facilitator@0.2.0 anchor --network $NET --org $ORG --facilitator-url <url> --session $SESSION
npx --yes @ixo/payouts-facilitator@0.2.0 anchor --network $NET --org $ORG --facilitator-url <url> --session $SESSION --yes

npx --yes @ixo/payouts-facilitator@0.2.0 deploy --network $NET --name $NAME --yes --json

npx --yes @ixo/payouts-facilitator@0.2.0 payout-wallet --name $NAME --network $NET --check

npx --yes @ixo/payouts-facilitator@0.2.0 admin oracles add did:web:<verifier host> \
  --url <url> --session $SESSION --network $NET

npx --yes @ixo/payouts-facilitator@0.2.0 admin defaults set --max 50.00 --currency USD \
  --approval-over 20.00 --rails stripe --label "Field payouts" \
  --url <url> --session $SESSION --network $NET

npx --yes @ixo/payouts-facilitator@0.2.0 admin team add did:ixo:<their address> --role approver \
  --url <url> --session $SESSION --network $NET

npx --yes @ixo/payouts-facilitator@0.2.0 trust-check --url <url> --org $ORG --network $NET --name $NAME

Set up a payouts facilitator for my company. Do the setup for me in this terminal. I only log in,
click and reply when you ask.

You are installing my company's own payouts service. It runs on our own Cloudflare account and pays
people from our own Stripe balance or Base USDC wallet. IXO never holds our keys.

Our details. Use exactly these:
- Company: <company name>
- Company entity: <did:ixo:entity:...>
- Network: <devnet | testnet | mainnet>
- Service name: <company>-payouts
- Rails: <stripe | usdc_base | stripe,usdc_base>
- Verifier oracles to trust: <did:web:...>

Rules:
- Run every command yourself, one at a time. Never ask me to type one. Run only the commands written
  here; if one fails, tell me what is missing in one plain sentence and stop.
- Write every command in full: no $P shorthand.
- Secrets never go into this chat. Never open, print or summarize a key or a secrets file. If I paste
  a key here, tell me to delete it in Stripe and make a new one.
- Where a command has a preview, run the preview first, tell me in one sentence what it will do, and
  go on when I say yes.
- Start each step with its check. If it is already done, say so and move on.
- At each STOP, tell me exactly what to do and wait for me. Open the page for me when there is one.
- Talk to me in plain words: "your payouts service", "your company".

Step 1. Check the computer
    node --version
It must say v24 or newer (Node 24 LTS or newer). If not, install the LTS from https://nodejs.org first.

Step 2. Log in to Cloudflare
    npx --yes wrangler whoami
If it is not logged in:
    npx --yes wrangler login
If the login has more than one account, ask which one is the company's and put
CLOUDFLARE_ACCOUNT_ID=<its id> in front of every command below.
STOP for me: a browser page opens. Sign in to Cloudflare and click Allow.

Step 3. Sign in as an owner of the company
Check who is signed in, without opening the file:
    node -e 'try{console.log(JSON.parse(require("fs").readFileSync(require("os").homedir()+"/.ixo/publish-session-<network>.json","utf8")).address)}catch{console.log("no sign-in")}'
If it says no sign-in, or the address is not mine:
    npx --yes @ixo/decision-oracle@0.4.0 login --network <network>
Never open, read or print ~/.ixo/publish-session-<network>.json.
STOP for me: a browser page opens. Sign in and type your PIN. You must be an owner of the company.

Step 4. Get Stripe ready (only when Rails includes stripe)
Stripe must have approved the company for Connect (https://dashboard.stripe.com/connect). If not, I
fill in Stripe's form and this setup stops until Stripe says yes.
Then I create a restricted key with: Transfers Write, Balance Read, Connected accounts Write,
Account links Write, Payouts Read, Balance transactions Read, Webhook endpoints Write. Everything
else None. On mainnet it starts with rk_live_, elsewhere rk_test_.
STOP for me: copy the new key, then say it is copied. Do not paste it into the chat.

Step 5. Install the payouts service
Preview (it changes nothing):
    npx --yes @ixo/payouts-facilitator@0.2.0 deploy --network <network> --name <service name> --entity <company entity> --rails <rails>
Then install. With stripe, read the key from the clipboard (macOS pbpaste; Linux wl-paste or
xclip -o; Windows PowerShell Get-Clipboard):
    STRIPE_SECRET_KEY="$(pbpaste)" npx --yes @ixo/payouts-facilitator@0.2.0 deploy --network <network> --name <service name> --entity <company entity> --rails <rails> --stripe-webhook --yes --json
Without stripe, the same command without STRIPE_SECRET_KEY and --stripe-webhook.
Clear the clipboard:
    pbcopy < /dev/null
Keep the url from the last line of the result. Below it is <url>.

Step 6. Link the service to the company
Preview, then the same with --yes:
    npx --yes @ixo/payouts-facilitator@0.2.0 anchor --network <network> --org <company entity> --facilitator-url <url> --session ~/.ixo/publish-session-<network>.json
    npx --yes @ixo/payouts-facilitator@0.2.0 anchor --network <network> --org <company entity> --facilitator-url <url> --session ~/.ixo/publish-session-<network>.json --yes
Install once more, so the service names its link:
    npx --yes @ixo/payouts-facilitator@0.2.0 deploy --network <network> --name <service name> --yes --json

Step 7. Fund the payout wallet (only when Rails includes usdc_base)
    npx --yes @ixo/payouts-facilitator@0.2.0 payout-wallet --name <service name> --network <network> --check
STOP for me: send USDC and a little ETH on Base to the address it prints, then say it is sent.

Step 8. Trust the verifier and set the payout limit
For each verifier:
    npx --yes @ixo/payouts-facilitator@0.2.0 admin oracles add <verifier did:web> --url <url> --session ~/.ixo/publish-session-<network>.json --network <network>
Ask: what is the most one payout can be, in dollars? And above what amount should a person at the
company approve each payout (or none)?
    npx --yes @ixo/payouts-facilitator@0.2.0 admin defaults set --max <most> --currency USD --approval-over <amount> --rails <rails> --url <url> --session ~/.ixo/publish-session-<network>.json --network <network>
Leave out --approval-over when I say none.
STOP for me: say the most one payout can be, and the amount above which you approve each payout.

Step 9. Check it
    npx --yes @ixo/payouts-facilitator@0.2.0 trust-check --url <url> --org <company entity> --network <network> --name <service name>
It must end with ok true. If not, say each problem in plain words and stop.

Step 10. Back up the secrets file
The file ~/.config/ixo-payouts/<service name>.secrets.json holds the keys of this service. It exists
only on this computer and at Cloudflare. Never open or print it.
STOP for me: copy that file into your password manager or another safe place. If it is lost, the
service must be set up again from scratch.

Step 11. Finish
If this setup signed in at step 3, offer to sign out. On yes:
    npx --yes @ixo/decision-oracle@0.4.0 logout --network <network>
Tell me the <url> of my payouts service, and that payouts are paid from our Stripe balance or
payout wallet, so it must hold money.