CoinPork

Payment readiness

Payment rails should be boring, verifiable, and reversible where possible.

CoinPork has configured a $9.95 USD monthly Stripe catalog, but public enrollment remains closed until the member backend and signed lifecycle webhooks are live.

No payment is accepted on this public prelaunch site.There is no active buy button, checkout link, membership charge, or crypto deposit address. Joining the waitlist is free.

Stripe card subscription

The live Stripe catalog contains one CoinPork Membership price at $9.95 USD per month. The planned checkout is Stripe-hosted recurring billing. It will open only after the production member database, authentication, signed webhook endpoint, cancellation flow, receipts, refund policy, and support process pass launch checks.

Hosted checkout instead of collecting card numbers on CoinPork
Signed lifecycle events before access is granted or renewed
Idempotent settlement records to prevent duplicate membership terms
Cancel-at-period-end behavior that preserves already-paid access

FaucetPay crypto payment

The operator reports that FaucetPay’s merchant API is approved and the account username is now configured as merchant_username. Its faucet API key is a separate payout credential. CoinPork will keep FaucetPay membership checkout closed until the production callback endpoint, callback-token verification, supported pricing currency, exact amount reconciliation, and manual-renewal behavior pass an end-to-end drill.

Membership and rewards stay separate

A membership payment purchases access to the service bundle. It does not purchase crypto, guarantee cash back, or create an investment return. Any future reward must have its own verified funding source, budget, eligibility rules, holds, and reversal process.

Before enrollment opens

  1. Deploy the member application and production database on a stable HTTPS origin.
  2. Register and verify the Stripe webhook endpoint.
  3. Run a complete subscription, renewal, cancellation, failure, refund, and dispute drill before accepting public payments.
  4. Publish final paid terms, refund policy, privacy updates, support response targets, and renewal disclosures.
  5. Enable the provider only after monitoring and reconciliation are ready.