How can I take payments from my white-label customers?

You take the money. We never charge your customers, never see your prices and never hold your gateway details — you tell us where your checkout is, and we send your customers there.

Nothing is added to a customer's account until you say the payment arrived. That is deliberate: coming back from a checkout only tells us a browser followed a link, which is not proof that anybody paid.

Setting up a place to pay

On your reseller panel, fill in Where customers buy more with the address of your own checkout. Anything that takes a payment works — a payment link, a hosted order page, an invoice page on your own site.

Set Searches per payment to how many searches one payment buys. Your customers then see a Get more searches item in their menu, and a page telling them what they are about to buy before they leave your site.

With Where customers buy more empty, none of this is offered at all — no menu item, no page. That is the switch for the whole thing.

Selling more than one package

If one figure is not enough, add plans on the panel. Each plan has:

Name — what the customer sees, such as Starter or Agency.
Price — free text, shown as you type it: $49 / month, €149, whatever you charge. We never read it as a number.
Searches — what buying it adds.
Emails per month — a sending cap to apply when they buy it. Leave it at 0 to leave their cap alone.
Checkout address for this plan — where this one is bought. Leave it blank and it uses Where customers buy more.

Most payment links are one per price, so a separate address per plan is usually what you want. Your customers then see your plans side by side instead of a single figure.

Turning a plan off stops it being offered. Payments already on their way still add what they bought.

What happens when a customer pays

1. They press Get more searches and see what they are buying, in your name.

2. They press Continue. We record the request, give it a short reference, and send them to your checkout.

3. They pay you, on your own checkout, in whatever way you have set up.

4. The request appears in the Payments section of your panel, with the customer, the number of searches and that reference.

5. You press Confirm once you can see the money. The searches are added immediately, and their allowance goes up.

Decline closes a request without adding anything, and it cannot be confirmed afterwards — use it for an abandoned checkout.

A customer with a request waiting sees that it is waiting for you, with the reference, so they do not pay twice.

Sending them back to your site afterwards

Optional. If your checkout lets you set a page to return to after payment, use:

https://yourdomain.com/dashboard/agency/success

It thanks them, tells them their searches are added once you confirm, and gives them a way back to their dashboard. Nothing is granted by it.

If your checkout cannot send them anywhere, nothing breaks. The request still reaches your panel and you still confirm it.

Adding searches automatically

If your own server can tell when a payment clears — a webhook from your gateway, for instance — it can add the searches itself and your customer never waits.

Send a POST to your own domain, with your API key in the body. Your key is on the reseller panel, and you can replace it there at any time.

POST https://yourdomain.com/dashboard/agency/renewal api_key your reseller API key email the customer's email address searches how many to add (optional)

Leave searches out and your Searches per payment figure is used. The reply is JSON, with ok set to true and the address and number it applied.

To stop a customer when a subscription of yours fails, and to put them back when it is paid:

POST https://yourdomain.com/dashboard/agency/suspend api_key your reseller API key email the customer's email address resume 1 to put them back

Important: the API key is the whole of the security on these two addresses. Keep it on your server, never in a page or in anything you send to a customer, and replace it on the panel if it is ever exposed.

Use POST and put the key in the body, not in the address. A key in a web address ends up in server logs and in the referrer of anything the page links to.