Rapay

Ra Pay — AI-Native Fiat Payments

Ra Pay is the first CLI-native payment platform built for AI agents. It lets you send compliant fiat USD payments using simple CLI commands. Every payment goes through Stripe's regulated infrastructure with full compliance screening.

This skill teaches you how to use the Ra Pay CLI to send business payments on behalf of your user.

Installation

npm install -g @rapay/cli

Verify installation:

ra --version

Expected output: ra-cli 1.5.0 or later.

One-Time Setup

Before sending payments, the user must complete account setup. The steps depend on whether they want to send, receive, or both.

Setup Paths

To Send: Add a Credit Card

ra add-card

This opens a Stripe Checkout page in the browser where the user securely saves a credit card. Once complete, the card is stored with Stripe (not locally) and payments can be sent immediately. No bank account or Stripe Connect onboarding is needed to send.

To Receive: Link a Bank Account

ra link-bank

This opens a Stripe-hosted flow in the browser where the user connects their bank account via Stripe Connect. Once complete, the CLI stores the session locally. This is required to receive payments — senders do not need this step.

To reconnect an existing verified account:

ra link-bank --account acct_XXXXXXXXX

Accept Terms of Service

ra accept-tos

The user must accept Ra Pay's Terms of Service before sending any payments.

Check TOS status at any time:

ra tos-status

Verify Account

ra whoami

Confirm the account shows as linked and verified before proceeding with payments.

Sending Payments

Ra Pay uses a two-step confirmation flow for every payment. This is mandatory — never skip the preview step.

Step 1: Preview the Payment

ra send <AMOUNT> USD to <RECIPIENT_ID> --for "<BUSINESS_PURPOSE>" --json

Example:

ra send 150 USD to acct_1A2B3C4D5E --for "Logo design work - Invoice #427" --json

This returns a fee breakdown without executing the payment:

{
  "status": "preview",
  "amount": 150.00,
  "currency": "USD",
  "recipient": "acct_1A2B3C4D5E",
  "fee": 3.00,
  "total": 153.00,
  "business_purpose": "Logo design work - Invoice #427"
}

Step 2: Show the Preview and Get User Approval

You MUST show the fee breakdown to the user and ask for explicit confirmation before proceeding. Never auto-confirm a payment.

Present the details clearly:

• Amount: $150.00
• Ra Pay fee (2%): $3.00
• Total charge: $153.00
• Recipient: acct_1A2B3C4D5E
• Purpose: Logo design work - Invoice #427

Step 3: Execute the Payment

Only after the user explicitly confirms, add the --confirm flag:

ra send 150 USD to acct_1A2B3C4D5E --for "Logo design work - Invoice #427" --json --confirm

The --confirm flag executes the payment. Without it, you always get a preview.

Amount Rules

• Minimum payment: $1.00
• Currency: USD only
• Recipients must be valid Stripe connected accounts (format: acct_ followed by alphanumeric characters)

Business Purpose Requirements

Ra Pay is a business-to-business payment platform. Every payment requires a --for flag with a legitimate business purpose (10–200 characters).

Valid Business Purposes

Good examples:

• "Freelance development work - Invoice #123"
• "API consulting services - March 2026"
• "Logo design work"
• "Website hosting fees - Q1 2026"
• "Content writing - 5 blog posts"

Business purposes should be specific and describe real goods or services rendered.

Blocked Patterns — Do NOT Use These

Ra Pay will reject payments with purposes that match these categories:

Peer-to-peer language — Ra Pay is not for personal transfers:

• friend, family, roommate, splitting bills, payback, loan, personal reimbursement

Gift language:

• gift, birthday, holiday

Money laundering red flags:

• gift cards, prepaid cards, cryptocurrency purchase, wire transfer

Vague or unspecific purposes:

• "for services" (too vague — specify what services)
• "payment" (not a purpose)
• "transfer" (not a purpose)

Gibberish or test strings:

• Repetitive characters (e.g., "aaaaaaaaaa")
• Random letters (e.g., "asdfghjkl")
• Repeated words (e.g., "test test test")

If a Purpose Is Rejected

Tell the user: "Ra Pay is for business transactions only. Please provide a specific business purpose describing the goods or services involved."

Help them rewrite their purpose to be specific and business-related.

Other Commands

Add or Update Payment Card

ra add-card

Opens Stripe Checkout in the browser to save or update a credit card for sending payments. The card is stored securely with Stripe, not locally.

To remove a saved card, use ra dashboard to open the Stripe Dashboard where the user can manage or delete their payment methods.

Check Balance

ra balance --json

Returns current balance, pending amounts, and payout schedule.

View Transaction History

ra history --json

Returns recent payments with timestamps and status. To show more transactions:

ra history --limit 50 --json

The --limit flag accepts values from 1 to 100 (default: 20 in CLI, 10 in MCP).

Account Info

ra whoami

Shows user ID, Stripe account status, verification status, and account tier.

Manage Refunds

ra refund

Opens the Stripe Dashboard in the browser for processing refunds. Refunds must be handled through the Stripe interface for security.

Manage Disputes

ra dispute

Opens the Stripe Disputes page. Remind the user: disputes must be responded to within the given timeframe or they auto-resolve against the user.

Open Stripe Dashboard

ra dashboard

Opens the full Stripe account dashboard in the browser. Use this for managing payment methods (including removing saved cards), viewing detailed transaction records, and account settings.

Unlink Account

ra unlink

Disconnects the Stripe account and clears the local session.

Using the --json Flag

Always use --json when calling Ra Pay commands. This returns structured JSON output that you can parse reliably instead of human-formatted text.

Commands that support --json:

• ra send ... --json
• ra balance --json
• ra history --json

Error Handling

• "Not linked" — The user hasn't set up a payment method. To send, run ra add-card. To receive, run ra link-bank.
• "TOS not accepted" — The user needs to run ra accept-tos.
• "Invalid business purpose" — The purpose was rejected by compliance screening. Help the user write a specific, business-related purpose.
• "Invalid recipient" — The recipient ID must match the format acct_ followed by alphanumeric characters.
• "Minimum amount" — Payment must be at least $1.00.
• "CLI version outdated" — The user needs to update: npm install -g @rapay/cli

Important Rules

1. Never auto-confirm payments. Always show the fee preview and get explicit user approval.
2. Never fabricate recipient IDs. Only use real acct_ IDs provided by the user.
3. Never bypass business purpose validation. If a purpose is rejected, help the user write a valid one.
4. Always use --json for structured output.
5. Ra Pay credentials stay local. Never ask users to share API keys, session tokens, or account IDs with you. Everything runs on their machine.