Беларуская 
Български 
Čeština 
Deutsch 
Español 
Français 
Magyar 
Italiano 
Nederlands 
Polski 
Português 
Română 
Русский 
Slovenčina 
Svenska 
Türkçe 
Українська PebbleHost billing & payments
PebbleHost hosts Minecraft, dedicated servers and Discord bots worldwide. Future clients should care about what I owned under the hood: a pluggable payment platform so customers pay invoices safely and staff operate gateways in test/live without chaos.
Problem
Invoices lived in an existing Yii control panel. Adding cards and PayPal as a one-off checkout would have forked billing. The domain needed a pluggable gateway with vaults, webhooks and refunds.
Stack
PHP, Yii, Stripe API, PayPal API, Payment Element, SetupIntents, webhooks, invoice billing.
Architecture
- Gateway layer on the invoice domain: Stripe Payment Element + PayPal Checkout
- Vaulted cards and PayPal methods; webhook handlers for both providers
- Client UX: pay unpaid invoices, manage saved methods, confirm into InvoiceService
- Staff ops: enable/disable gateways, test/live, transaction log, full/partial refunds
- Regression coverage around intents, webhooks and manual-payment edge cases
Result
Customers pay inside the panel they already use. Integrono's pattern here is payment-platform work: gateways you can monitor and roll back, not a Stripe snippet on a landing page.
Stack
Free discovery call
Bring a messy stack or stalled integration - Integrono will map the smartest first move.
You get a senior take on budget traps, dependencies and whether to buy, glue or build - before paid work starts. The CEO stays in the loop.