Available resources
Every command follows the patternfintoc <resource> <action> [flags]. The CLI supports these resources and actions:
Make an API request
The general form isfintoc <resource> <action> [flags]. Run fintoc --help to list available resources, or fintoc <resource> --help for the actions supported on that resource.
--json for machine-readable output:
v2 transfers create requires a JSON Web Signature (JWS) private key for signing. Provide it via the --jws-private-key flag or set jws_private_key in ~/.fintoc/config.toml. To generate a key pair, see Generate JWS Keys.Pass a JSON payload
Forcreate commands, pass a payload file with --from-json, or pipe one in with -:
--from-json. Flag values take precedence over JSON keys. Objects deep-merge, but the CLI replaces arrays wholesale.
Delete a resource
Delete commands ask for confirmation before removing the resource. Pass--yes to skip the prompt, which is useful in CI.
Trigger test events
fintoc trigger fires a test event against your account, which exercises webhook handlers without producing real activity.
--override accepts dot-notation (metadata.order_id=abc123) and is repeatable. The same precedence rules as --from-json apply.
Listen to webhooks on localhost
fintoc webhooks listen opens a WebSocket connection to Fintoc and forwards events to your local server. The CLI signs each forwarded request so your existing signature verification keeps working without a public tunnel.