Plorea Laravel Package

Use this skill when building embedded or native checkout with the Plorea SDK (memberflow/plorea): mounting Adyen Drop-in on your own domain, paying or storing cards from an iOS or Android app with Adyen's native SDK, building the backend endpoint that opens a Plorea session for a browser or app, handling Adyen return URLs, redirectResult, universal links / App Links, the Adyen client key (PLOREA_ADYEN_CLIENT_KEY), CSP for Adyen, Apple Pay / Google Pay, or App Store payment rules. Covers Channel, payByLink()->session(), paymentMethods()->setup()->channel()->session(), toCheckout(), and verifying results server-side.

Use this skill when preparing a Plorea Payments integration (memberflow/plorea) for production: switching from test to live, live API keys and PLOREA_ENVIRONMENT, registering the production webhook and its signing secret, merchant KYC before launch, retry and idempotency settings, monitoring Plorea requests, live Adyen client keys and whitelisting for embedded or native checkout, or running a first real transaction. Also use when reviewing a Plorea integration for launch readiness.

Use this skill when working with the Plorea Payments SDK (memberflow/plorea) in a Laravel app. Trigger when creating or handling payment links, checking payment status, refunding or cancelling payments, storing cards / payment methods, creating or managing subscriptions, handling Plorea webhooks, or testing Plorea integrations with Plorea::fake(). Covers the Plorea facade, Amount minor units, firstOrCreate and PaymentAlreadyPaidException, merchant KYC onboarding, webhook signature verification, and the fake client's assertions and stubs.

Use this skill when building or reviewing recurring billing on the Plorea Payments SDK (memberflow/plorea) in a Laravel app: memberships, plans or seats billed to a stored card. Trigger when starting a subscription from a saved card, deciding when to grant access, activating on the first charge, handling trials or delayed start dates, building dunning for failed recurring charges, cancelling, pausing, changing plan, price or card, avoiding duplicate subscriptions, or writing the scheduled reconciliation job. Covers the lifecycle and the state your own app must keep; for the individual API calls use the plorea-payments skill.