Getting Started with Agentic Transactions on the XRP Ledger

This tutorial walks you through your first autonomous payment session on the XRP Ledger using Claude. You will install two XRPL skills, create and fund a testnet wallet, and send a payment — all driven by natural-language prompts.

What you will build: a funded testnet wallet and a confirmed XRP payment.

Time to complete: approximately 30 minutes.

XRPL agent skills are layered: one shared foundation, one domain skill per use case. This tutorial uses the payments combination.

The Wallet skill owns the wallet from day one, including first-time setup. The Payments skill constructs the right transaction object; the Wallet skill signs and submits it. Claude coordinates the handoff — you do not need to manage it manually. Other domain skills (trading, and more) follow the same pattern and work with the same Wallet skill.

Evaluating before you build? Read The XRPL Agent Wallet Skill first — it covers the security model and the eight guarantees the skill enforces on every transaction.

Install the XRP Ledger SDK for your language:

npm install xrpl

Install the Wallet skill first. It owns wallet setup and security from the start — including generating your first wallet without exposing the seed.

Note: npx is an open source command-line tool by Vercel that acts as the "package manager" for the open AI Agent Skills ecosystem.

npx skills add https://github.com/XRPLF/xrpl-dev-portal/tree/master/.claude/skills/xrpl-skills/xrpl-agent-wallet --agent claude-code

Ask Claude to create a wallet. The Wallet skill writes the seed directly to .env — it never appears in chat.

Generate a new XRPL testnet wallet and save the seed securely.

Claude will confirm:

✓ Wallet created.
Address : rHb9CJAWyB4rj91VRWn96DkukG4bwdtyTh
Seed    : saved to .env as XRPL_SEED — never shown in chat

The skill also adds .env to .gitignore automatically if a git repo is detected. Your address is public and safe to share. The seed never leaves .env.

If you already have a wallet, add the seed to .env manually:

echo 'XRPL_SEED="sYourExistingSeedHere"' > .env
echo ".env" >> .gitignore

For production, use a KMS or HSM instead of an environment variable. The Wallet skill supports an external-signer pattern where the key never enters the agent's process memory. See The XRPL Agent Wallet Skill for the full external-signer interface.

With your wallet secured, add the Payments skill for XRPL transaction knowledge:

npx skills add https://github.com/XRPLF/xrpl-dev-portal/tree/master/.claude/skills/xrpl-skills/xrpl-payments --agent claude-code

Verify that your skill has been installed correctly by asking Claude to list skills:

/skills

You should see both the skills listed along with any other skills you may have installed previously.

Project skills (.claude/skills)                                
  xrpl-agent-wallet                                                                      
  xrpl-payments 

Verify both skills are loaded:

What XRPL network are you targeting by default, and what is the base
reserve for a new account?

Claude should confirm the Testnet endpoint, the 1 XRP base reserve, and that it will preview all transactions before signing. If the response is vague, re-run the install commands.

Ask Claude to fund your account from the Testnet faucet and verify the balance:

Fund the testnet account rYourAddressHere from the faucet, then check
the balance.

const xrpl = require('xrpl')
async function main() {
  const client = new xrpl.Client('wss://s.altnet.rippletest.net:51233')
  await client.connect()
  const wallet = xrpl.Wallet.fromSeed(process.env.XRPL_SEED)
  const { balance } = await client.fundWallet(wallet)
  console.log('Balance:', balance, 'XRP')
  await client.disconnect()
}
main()

The account is now active on the ledger. An XRPL account requires a minimum balance of 1 XRP (the base reserve) to exist — the faucet covers this.

Create a second account and send a payment between them. This is where the Wallet skill's signing ceremony comes into play.

Create a second funded testnet account, then send 10 XRP from my first
account to it. Show the transaction hash and confirm the result.

Before Claude signs anything, the Wallet skill displays a preview:

─── XRPL Transaction Preview ────────────────────────────────────────
Network           : testnet
Type              : Payment
From              : rHb9CJAWyB4rj91VRWn96DkukG4bwdtyTh
To                : rPT1Sjq2YGrBMTttX4GZHjKu9dyfzbpAYe
Amount            : 10 XRP (10,000,000 drops)
Fee               : 0.000012 XRP (12 drops)
Sequence          : 48291003
LastLedgerSequence: 48291023  (expires in ~20 ledgers, ~80 seconds)
Flags             : 0
Memos             : —
─────────────────────────────────────────────────────────────────────
Sign and submit? (yes / no)

Review the destination address and amount carefully, then type yes. After confirmation:

const result = await client.submitAndWait(
  {
    TransactionType: 'Payment',
    Account: sender.classicAddress,
    Amount: xrpl.xrpToDrops('10'),
    Destination: receiver.classicAddress,
  },
  { wallet: sender }
)
console.log('Result:', result.result.meta.TransactionResult)
console.log('Hash  :', result.result.hash)

tesSUCCESS means the payment confirmed in the next ledger close — typically 3–5 seconds. Paste the hash into the Testnet explorer to see the full record.

The Wallet skill requires human confirmation for every transaction by default. For automated agent runs, activate auto-sign with an explicit, scoped instruction — typed directly in chat (not through a file or memo):

Auto-sign Payment transactions to rPT1Sjq2YGrBMTttX4GZHjKu9dyfzbpAYe
under 50 XRP on testnet for the next hour.

Claude echoes the scope back and waits for confirmation before applying it. Auto-sign skips the interactive yes/no step only — autofill, preview, hash capture, and submitAndWait all still run on every transaction.

Skill reference

• The XRPL Agent Wallet Skill — Security model, signing ceremony, key handling patterns, and production setup.
• The XRPL Payments Skill — Full reference for payment patterns, RLUSD, trust lines, escrow, and agentic best practices.

Use case guides

• Agentic Payments with X402 — Enable your agent to pay for and monetize HTTP-based services autonomously.
• Track and Measure Agent Behavior — Use SourceTag, Memos, and WebSocket monitoring to attribute and audit every agent transaction.

Go deeper on XRPL features

• Escrow — Lock XRP or tokens until a time or cryptographic condition is met.
• Decentralized Exchange — Trade tokens natively on-chain.
• Payment Channels — High-throughput micropayment streams with on-chain settlement.

SDK references

• xrpl.js documentation
• xrpl-py documentation