card-issuing-quickstart — 3-Step MVP Loop

Download card-issuing-quickstart.zip · Part of the MVP bundle.

Purpose

Guides the AI tool through the end-to-end minimum integration loop — enough to verify authentication, public headers, field semantics, and response handling all work correctly.

The 3 steps

#	API	URL path	Purpose
1	CardApplication	POST /cardmgr/cardApply	Open a card → receive cardToken + expiryDate + CVV2
2	CustomerCardInfoInquiry	POST /custmgr/inquiryCardListByCIF	Look up cards by customerId — assert the new cardToken appears in cardList
3	CardActivation	POST /cardmgr/cardActivate	Activate the card (state transitions N → U)

Why these 3?

They cover write → read → write across two modules (cardmgr + custmgr), exercising:

• Bearer token authentication
• Public header injection (9 common fields)
• Request/response field semantics for Application, Customer and Card modules
• Business responseCode == "00" success check

Once this loop runs end-to-end, the rest of the API surface follows the same pattern.

Prerequisites the Skill asks for

The Skill prompts the developer to obtain these from Coshine before writing code:

1. API_BASE_URL (sandbox: https://march.sandbox.efaka.net/card-api)
2. Bearer Token
3. participantId
4. tranBranch
5. cardProdCode (sandbox Visa = 2201, Mastercard = 5200)

Test strategy (language-agnostic)

The Skill describes protocol-level verification using any HTTP client — curl, Postman, or a native HTTP library in the developer's language. A Python reference implementation is available in the source repository under reference-impl/ as one example, not as a requirement.

Depends on

• card-issuing-auth
• card-issuing-references

Source

See skills/card-issuing-quickstart/SKILL.md in the repository for the authoritative content.