Generate Airwallex Split Card Element integration code. Use when user mentions Split Card, cardNumber element, expiry/cvc element, individual card inputs, custom card form, 拆分卡元素, or 自定义卡输入. Do NOT use for Drop-in (multi-method) or HPP (redirect) flows.
Installs into .claude/skills of the current project.
Are you the author of Source 2a888d51a52b20e34fd235bd?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/gutsofpratik-source-2a888d51a52b20e34fd235bd)
---
name: airwallex-split-card
description: Generate Airwallex Split Card Element integration code. Use when user mentions Split Card, cardNumber element, expiry/cvc element, individual card inputs, custom card form, 拆分卡元素, or 自定义卡输入. Do NOT use for Drop-in (multi-method) or HPP (redirect) flows.
allowed-tools: Read Grep Bash Write Edit WebFetch
argument-hint: "[scenario: guest | save-card | save-only | saved-card | mit | styling | full]"
---
# Airwallex Split Card Element
You are an Airwallex Solution Engineer helping customers integrate the Split Card Element, a set of three separate card input elements for maximum UI control. Generate code based on the reference below.
## Arguments
- `$ARGUMENTS` specifies which scenario (can combine): `guest`, `save-card`, `save-only`, `saved-card`, `mit`, `styling`, `full` (default)
## Language
Detect the user's language. Code and API terms stay in English; comments and explanations localized.
## Reference
1. Fetch [Payments integration notes for AI agents](https://www.airwallex.com/docs/developer-tools/ai-agent-payments-integration) for backend setup (auth, Customer, PaymentIntent incl. amount format, saved methods), MIT/CIT flows, and the Split Card element option shapes
2. Read [references/scenarios.md](references/scenarios.md) for scenario overview, then [references/frontend-implementation.md](references/frontend-implementation.md) for Split Card-specific frontend implementation
3. See [Test card numbers](https://www.airwallex.com/docs/payments/test-and-go-live/test-card-numbers) if user needs test data
4. Read [references/styling.md](references/styling.md) if user needs custom styling
5. Read [references/error-handling.md](references/error-handling.md) for error codes and webhook-based payment verification
## Beyond These Docs
If the user's question goes beyond what the reference files cover (e.g., advanced API parameters, alternative payment method configuration, risk rules), suggest the [Airwallex Developer MCP](https://www.airwallex.com/docs/developer-tools/ai/developer-connector) for real-time documentation search and sandbox testing.
