External Laravel consumer
Biqli Stripe attribution harness
Test a real short-link click, SDK signup lead, Stripe Checkout, webhook sale, subscriptions, trials, renewals, cancellations, and refunds.
Step 1
Attribution
- Browser click ID
- Checking...
- Server click ID
- No attribution captured
- Stripe target
- acct_1UKZ3FRvvJHSL2Mq ยท sandbox
Original PHP SDK smoke controls
These remain available for isolated server SDK lead and custom-sale tests.
Smoke customer: laravel-customer-9514bb63-d78f-45a1-a811-c846e3366584
Step 2
Unlock sandbox operations
- Stripe secret key
- Configured server-side
- Stripe publishable key
- Configured
Step 3
Real signup
Creates a Stripe Customer, then records a trusted server-side lead using that Stripe customer identity.
Step 4
Stripe Checkout
Biqli stores the Checkout mapping in the browser immediately before redirecting to Stripe.
Step 5
Lifecycle operations
After Checkout returns, refresh first. Then run refund, trial, renewal, or cancellation scenarios and verify the resulting Biqli customer activity.
Trial
End the active trial now to generate its first paid invoice.
Evidence
Current harness state
[]
Manual edge cases
Checkout outcomes to verify
- Success: use card
4242 4242 4242 4242. - Decline: use Stripe's generic-decline test card and confirm no sale appears.
- 3DS: use Stripe's authentication-required test card and complete the challenge.
- Abandonment: open Checkout, then return without paying; the mapping should expire without a sale.
- Duplicate delivery: resend a delivered event in Stripe Workbench; totals must remain unchanged.
- Trial semantics: signup plus Stripe trial intentionally creates a signup lead and a free-trial lead.