What problem does it solve? Adding Apple, Google, and Samsung wallet credentials to an existing product requires coordinating SDK selection, database schema changes, secrets management, billing wiring, lifecycle endpoints, and webhook handling — a process that is easy to get wrong (duplicate issuance, unencrypted tokens, missed webhook events) without a structured plan. ## Core Features & Use Cases - Eight-phase guided integration: language/SDK selection, design session (MVP / Essential / Complete / Premium levels plus UI/API choice and billing model), database discovery against four canonical concepts, migrations, secrets and client wiring, billing integration, endpoints and lifecycle, and webhook handling. - Per-language SDK references: install commands, client init, provisioning and lifecycle method signatures, webhook receivers, and encryption-at-rest patterns for JavaScript/TypeScript, Ruby, Go, Python, C#/.NET, Java, and PHP, plus a porting guide for stacks without an official SDK. - Snapshotted AccessGrid references: HMAC-SHA256 API authentication (X-ACCT-ID / X-PAYLOAD-SIG), pass state transitions, image dimension requirements, webhook event catalog, and billing patterns for Stripe, Spreedly, Authorize.net, Chargify, Adyen, and Checkout.com. - Use Case: A Rails SaaS team wants to issue mobile wallet access passes to its users. The skill walks them through picking the Essential level, mapping their users/credentials tables, adding accessgrid_id and state columns, wiring the Ruby SDK, and standing up a deduplicating webhook receiver. ## Quick Start Ask the agent to integrate AccessGrid mobile wallet credentials into your existing application and answer its questions about language, integration level, and billing model.