🌐 Language / 语言: English | 中文

A skill for integrating WorldFirst APIs with LLM or Agent frameworks. Supports Java, Golang, and Python code generation, covering Transfer, Payout, Beneficiary Management, Account Management, Statement Management, and Trade Order Management — with built-in RSA256 signing and production-grade templates.

Quick Start | Supported Modules | Browse References

• What Problem Does This Solve
• Supported Modules
• Quick Start
• Directory Structure
• Module Details
• Common Infrastructure
• Signing Algorithm
• Important Notes

WorldFirst provides a comprehensive set of cross-border payment, fund transfer, and account management APIs. However, integrating these APIs involves complex steps including RSA256 signing, request/response model construction, error handling, and multi-language boilerplate code.

This skill packages WF API integration knowledge into standardized templates that AI can read and generate code from. Developers can integrate WF APIs in Vibe Coding mode — simply describe your requirements in natural language, and the skill helps AI to:

• Select the right API — Match the most appropriate endpoint based on your business scenario
• Generate production-grade code — With correct signing, error handling, and coding standards
• Avoid common pitfalls — Such as hardcoded keys, missing signature verification, idempotency issues, etc.

Note: Python currently only supports the common module (common/) and Statement Management (statement-management/). Other modules do not have Python templates yet.

Determine which WF API module you need:

• Transfer — Fund transfers between WorldFirst accounts
• Payout — Payments to third-party bank accounts or e-wallets (payroll, supplier payments, etc.)
• Beneficiary — Manage beneficiary bank card information
• Account — Query account balance, info, quota, sub-users, stores; receive notifications
• Statement — View transaction records and reconciliation
• Trade Order — Upload trade orders for B2C settlement or B2B association

Each module contains specific endpoints. See Module Details below for the full list.

Before code generation, you need to provide:

• Project path — Target location for generated code
• Programming language — Java, Golang, or Python
• Base package / module name — e.g., com.example.project (Java), github.com/example/project (Go), wf_integration (Python)
• WF credentials — Client ID, User ID, API base URL, RSA key paths

The skill generates code based on your configuration, then performs a post-generation checklist to ensure correctness.

wf-api-integration/
├── SKILL.md                          # Skill definition and instructions
├── README.md                         # This file
└── references/                       # All reference code and guides
    ├── common/                       # Common infrastructure (signing, config, HTTP client, models)
    │   ├── golang/
    │   ├── java/
    │   ├── python/
    │   └── README.md
    ├── transfer/                     # Transfer module
    │   ├── consult-transfer/
    │   ├── create-transfer/
    │   ├── inquiry-transfer/
    │   ├── notify-transfer/
    │   └── README.md
    ├── payout/                       # Payout module
    │   ├── consult-payout/
    │   ├── create-payout/
    │   ├── inquiry-payout/
    │   ├── notify-payout/
    │   ├── field-reference.md
    │   └── README.md
    ├── beneficiary/                  # Beneficiary management
    │   ├── inquiry-template/
    │   ├── bind/
    │   ├── remove/
    │   ├── edit/
    │   ├── inquiry-list/
    │   ├── notify-bind/
    │   └── README.md
    ├── account-management/              # Account management
    │   ├── inquiry-account/
    │   ├── inquiry-balance/
    │   ├── inquiry-available-quota/
    │   ├── inquiry-subuser/
    │   ├── inquiry-store/
    │   ├── notify-vostro/
    │   ├── notify-balance-change/
    │   └── README.md
    ├── statement-management/            # Statement management
    │   ├── inquiry-statement-list/
    │   ├── inquiry-statement-detail/
    │   └── README.md
    └── trade-order/                  # Trade order management
        ├── submit-trade-order/
        ├── inquiry-trade-order/
        ├── notify-trade-order/
        ├── field-reference.md
        └── README.md

Each endpoint directory contains:

• GUIDE.md — API specification and integration guide
• java/ — Java code templates
• golang/ — Golang code templates
• python/ — Python code templates (available for some endpoints)

All modules share the following components located in references/common/:

All WF APIs use RSA256 signing. The signing content format:

POST {apiPath}\n{clientId}.{requestTime}.{requestBody}

See references/common/ for signing utility code in each language.

1. Be specific about your business scenario — When describing requirements to AI, specify the exact business scenario (e.g., "transfer between WorldFirst accounts" or "pay to a bank card") to avoid ambiguity.
2. Always review generated code — Verify logical correctness before deploying to production.
3. Never hardcode keys — RSA private keys, clientId, and secretKey must be loaded via file paths, environment variables, or key management services. Never store them in source code.
4. Always verify signatures — Verify signatures on every WF API response and async notification to prevent man-in-the-middle attacks.
5. Ensure idempotency — Use unique transferRequestId / payoutRequestId for fund operations to prevent duplicate charges from retries.
6. Use HTTPS only — All API requests must use HTTPS. Never use HTTP.
7. Don't assume final results — After initiating a transfer or payment, always confirm the final status via inquiry endpoints or async notifications. Never rely solely on the request response status.
8. Separate production and test keys — Production and test environments must use different clientId and key pairs.