raven-transfer_skill

Overview

This skill provides wallet-aware Raven Atlas NGN payout operations for safe, idempotent transfers to bank beneficiaries and merchant settlement accounts. It enforces pre-transfer balance checks, account resolution, explicit confirmation tokens, and normalized result reporting. Use it to prevent duplicate debits and to maintain deterministic payout workflows.

How this skill works

The skill inspects the NGN wallet balance before any transfer and resolves recipient account names from account number plus bank or bank code. It supports previewing transfers to obtain a confirmation token, then requires an explicit confirm flag to execute the transfer exactly once. After execution it returns normalized fields like available_balance, fee, total_debit, status, and raw_status.

When to use it

• When executing single or merchant NGN payouts where duplicate debits must be prevented
• When you must verify wallet funding before attempting any transfer
• When recipient account names must be resolved and validated prior to payout
• When business rules require explicit, auditable confirmation tokens for money movement
• When you need normalized transfer results for downstream reconciliation

Best practices

• Always run the balance command and confirm available_balance covers total_debit plus fee before previewing a transfer
• Use the lookup command to resolve and log account name matches; do not transfer without a resolved name
• Obtain and store the transfer preview confirmation token; require manual or programmatic explicit confirm before executing
• Do not auto-retry transfer submissions; follow idempotency rules and check transfer-status for finality
• Keep RAVEN_API_KEY in the agent runtime and restrict its access to authorized processes only

Example use cases

• Payout salary or vendor NGN transfers where reconciliation requires normalized fee and status fields
• Merchant settlement transfers routed to merchant settlement accounts with resolved account names
• Automated payout flows that gate execution on explicit human approval via confirmation token
• Failure-handling scripts that query transfer-status to detect reversals or final states before retrying at higher workflow level