Agent Skills Use Cases

Pine Labs Agent Skills help AI coding assistants turn natural-language requests into Pine Labs-aware implementation guidance. Each example below shows the prompt a developer gives the assistant and how the installed skills help route the request toward the right flow, safeguards, and API references.

Integrate Payment Gateway through your AI coding assistant

1. Add a hosted checkout flow

Prompt: "Create a Pine Labs hosted checkout integration in UAT for my backend and frontend."

The assistant loads the Pine Labs best-practices skill, then routes to the Checkout and Orders references. It helps generate:

• A backend-first order creation flow
• Server-side token generation using PINELABS_CLIENT_ID and PINELABS_CLIENT_SECRET
• A checkout order request in REDIRECT mode
• A return or callback handling path for post-payment verification

→ The result is a safer hosted checkout implementation aligned to Pine Labs payment flow expectations.

2. Review a webhook before go-live

Prompt: "Review my Pine Labs webhook handler and check whether it is secure enough for production."

The assistant routes to the webhook-related best-practices guidance and reviews the code for:

• Signature verification before processing events
• Idempotency protection for duplicate or replayed events
• Trusted server-side payment confirmation patterns
• Unsafe assumptions in event handling or fulfillment logic

→ The result is not just code review, but payment-aware review focused on high-risk implementation gaps.

3. Create a payment link flow

Prompt: "Generate a Pine Labs payment link flow with expiry and merchant reference tracking."

The assistant routes to the Payment Links reference and helps scaffold:

• Payment link creation logic
• Expiry handling
• Merchant reference mapping
• Safer backend usage patterns for link generation and retries

→ The result is a more complete payment link flow rather than only a single API call.

4. Add refund handling with idempotency

Prompt: "Create a Pine Labs refund workflow and explain the idempotency strategy."

The assistant routes to the Refunds guidance and helps developers:

• Structure refund requests safely
• Add idempotency keys or request IDs
• Avoid duplicate money-moving actions during retries
• Document what should be verified before refund execution

→ The result is a refund workflow that is safer for real-world financial operations.

5. Build subscriptions and recurring payment flows

Prompt: "Set up Pine Labs subscription plans and recurring billing flow for my application."

The assistant loads the Subscriptions references and helps with:

• Plan creation and lifecycle setup
• Subscription creation and updates
• Debit presentation and retry flow guidance
• UAT-first implementation patterns for recurring payments

→ The result is more reliable recurring billing guidance across plans, subscriptions, and debit flows.

6. Check settlement and reconciliation logic

Prompt: "Help me reconcile Pine Labs settlements using UTR details and order references."

The assistant routes to the Settlements and Orders references and helps explain:

• How settlement data maps to payment activity
• How to track transactions through identifiers such as merchant references and UTR details
• What backend checks or reconciliation steps should be added

→ The result is more structured support for finance and operations workflows, not only checkout implementation.

7. Run a go-live readiness review

Prompt: "Review my Pine Labs integration before production launch."

The assistant uses the shared Pine Labs best-practices skill to check for issues such as:

• Production vs UAT environment mistakes
• Secrets or tokens exposed in frontend code
• Missing webhook verification
• Missing idempotency on refunds, payouts, or other state-changing calls
• Gaps in server-side payment confirmation

→ The result is a more disciplined pre-launch review for payment integrations.

8. Generate an access token

Prompt: "Generate an access token for Pine Labs APIs."

The assistant routes to the getting-started guidance and helps with:

• Dashboard signup and API key setup
• OAuth token generation using PINELABS_CLIENT_ID and PINELABS_CLIENT_SECRET
• Secure credential handling patterns
• Environment variable setup for UAT and production

→ The result is a safer credential and token flow with secrets kept server-side.

9. Add mobile SDK integration

Prompt: "Add Pine Labs mobile SDK integration to my Android app."

The assistant first asks for the platform if not specified (Android, iOS, or Flutter), then routes to the platform-specific mobile SDK guidance and helps with:

• SDK installation and initialization
• Callback handling and verification
• Cancellation and interruption recovery
• Backend payment status verification

→ The result is a complete mobile SDK integration with proper callback handling.

10. Migrate from another payment provider

Prompt: "Migrate my existing Razorpay checkout integration to Pine Labs."

The assistant routes to the migration guides and helps with:

• Credential and lifecycle mapping
• Webhook event mapping
• Refund and reconciliation flow differences
• Legacy order routing and dual-run reconciliation
• Rollback planning

→ The result is a safer migration path with concept mapping and rollback options.

11. Use P3P for agent payments

Prompt: "Use P3P to create a UPI ReservePay mandate and execute a sandbox debit."

The assistant routes to P3P guidance and helps with:

• CLI authentication and setup
• Mandate creation for UPI ReservePay
• PPT token creation
• Debit execution with sandbox-first safety
• Webhook listening for payment events

→ The result is a working P3P agent payment flow with sandbox validation.

12. Integrate P3P x402 middleware

Prompt: "Integrate P3P x402 middleware into my Next.js app without exposing client secrets."

The assistant routes to P3P SDK integration guidance and helps with:

• Framework template selection (Next.js, Express, Python)
• Server-side secret handling
• 402 challenge and retry flow wiring
• Sandbox test data setup

→ The result is a secure x402 integration with secrets kept server-side.

---

Next steps