Integration service
FunPay × FazerCards Reseller
Hosted panel: FunPay lots map to FazerCards Reseller SKUs; paid FunPay orders become Reseller API orders. Below: two fulfilment paths — top-ups vs codes/cards.
How it works
From activation to automated delivery
Activation → map lots → Reseller order → buyer chat update.
Activation
Sign up, open the «Add-ons» page in your panel and switch the integration on — access is enabled automatically, no tickets or waiting.
Lots & SKUs
Bind each FunPay lot to a Reseller product and params (currency, face value, etc.).
FazerCards order
After FunPay payment the integration creates and tracks the order on your Reseller account.
Done in chat
When fulfilment finishes the buyer gets your template message (plain text; includes codes when the flow is code delivery).
Capabilities
What you get
What the product does — in short.
Panel
Orders and lots in the browser; works on phone too. No VPS “bot host” required.
Lot → Reseller SKU
Each FunPay lot points at a specific FazerCards Reseller product/settings — fulfilment debits your Reseller balance via API.
FunPay login
Automation-style onboarding inside the integration — no extra public credential form on our marketing site.
Proxy required
Outbound FunPay traffic goes through your proxy — required for the integration; you set the parameters in the integration settings.
Logs
Order + event history to reconcile FunPay vs FazerCards quickly.
Chat & templates
FunPay chat copy is yours to edit; for top-ups we may collect buyer details in-thread when the section is set up that way.
Sections
Top-ups vs keys / gift cards
Two different paths: where required data comes from and what you send in chat depends on the section.
Top-ups
Connect the lot to the top-up section. Required fields (login, ID, etc.) either come from the lot description or we ask the buyer in chat — per section settings.
Once we have data, we place the FazerCards Reseller order and wait for completion. Then we close the line and tell the buyer the order is done.
Keys & gift cards
The lot is tied to specific FazerCards Reseller catalogue items. On FunPay payment we know what and how much was bought from the lot↔SKU mapping.
We buy via Reseller; when FazerCards returns keys or codes we paste them in chat as plain text and confirm the order is complete.
Also in the panel
Rules — short
For normal post-payment delivery — not policy evasion.
Events & orders
The service reads FunPay events (orders, chats) and places matching orders in FazerCards — standard for this kind of connector.
Proxy
Your proxy is mandatory: FunPay requests don’t “just leave our datacenter IP”.
FunPay
Follow FunPay terms. You’re responsible for listings and buyer comms.
Logs
Orders and events are recorded: timestamps, statuses, FunPay ↔ FazerCards linkage — handy for disputes.
Messages
Edit chat templates: completed, errors, prompts when you need buyer data.
More panel sections will roll out over time; the two flows above stay the backbone.