Virtual CardsWorks with any FleetProxy planAbout 10 minutes

How to Use FleetProxy with Pay2.house

Pay2.house issues virtual payment cards for exactly the work proxies get used for: running advertising accounts on Google, Meta and TikTok, paying for subscriptions, and keeping team spend separated. It has no proxy settings of its own, and does not need any. It sits one layer above the proxy. The proxy decides where your connection appears to come from; the card decides what your payment looks like. Platforms check both, which is why running one without the other leaves an obvious gap.

$15 added to your Pay2.house bonus balance

Get your proxies Sign up with Google

An active FleetProxy plan (residential rotating, static residential, mobile rotating, or datacenter)
An antidetect browser to hold the profiles, such as AdsPower, BitBrowser or Afina
A Pay2.house account with a funded balance

Not sure which proxy type fits? Rotating residential works for most multi-account setups, while static IPs suit accounts you keep long term.

Get Your FleetProxy Credentials

Every browser profile you pair with a card needs a host, port, username, and password. Here is where to find them in the dashboard.

1
Open Active Proxies
Log in to the FleetProxy dashboard and click Active Proxies in the left sidebar. It lists every plan you already own.
2
Manage the plan you want to use
Find the product you are connecting, then click Manage. Each product has its own host and ports, so pick the one you actually plan to route traffic through.
3
Generate and copy your proxy
Open the Generator tab. Choose country, state, city, or ISP if you need a specific location, pick HTTP/HTTPS or SOCKS5, then set rotation to Random IP or Sticky IP. Your credentials appear on the right, ready to copy.

Host and port for every product

FleetProxy host and port by product
Product	Host	HTTP / HTTPS	SOCKS5
Residential Rotating	residential-v2.fleetproxy.io	5000	5000
Mobile Rotating	mobile.fleetproxy.io	5000	5000
Datacenter Rotating	datacenter.fleetproxy.io	9000	9000
Static Residential (ISP)	Your assigned IP address	50100	50101

Using Pay2.house with FleetProxy, Step by Step

1
Give the profile its own IP first
Set your FleetProxy credentials in the browser profile that will run the account. Static residential suits an account you intend to keep, because the address does not change underneath it. The AdsPower, BitBrowser and Afina guides on this site cover the exact fields for each.
2
Issue a card in Pay2.house for that one profile
Open Pay2.house and issue a virtual card. It offers BINs issued in a number of countries, so choose one that matches the country your proxy is in. A card issued in one country, paid from an IP in another, is one of the easier mismatches for a platform to spot.
3
Add the card from inside the profile, never outside it
Enter the card on the advertising platform from within the browser profile that holds its proxy. Adding it from your own browser attaches your real IP to that payment method, which is precisely the link the proxy was there to prevent.
4
Keep it one profile, one IP, one card
Reusing a card across profiles undoes the isolation the proxies gave you. Payment method is one of the strongest signals a platform has for tying accounts together, and it survives a perfect fingerprint. Issue a fresh card per profile and keep the mapping written down somewhere.
5
Fund before the campaign, not during it
Pay2.house tracks spend across every card you issue, so per-account cost is visible without opening each profile. Top the balance up ahead of a launch rather than mid-flight, since a decline part-way through reads as a payment problem on the platform side.

If you are using static residential (ISP) proxies

For static residential (ISP) proxies there is no gateway domain to use. Put the IP address assigned to you in the dashboard into your browser profile, then set the port to 50100 for HTTP or 50101 for SOCKS5. Static addresses suit accounts you plan to hold for months, which is usually the same set of accounts worth giving a dedicated card.

Verify It Actually Works

Open httpbin.org/ip inside the launched profile and confirm the address it reports is your FleetProxy IP rather than your own. Then check the card country in Pay2.house against the proxy country. Those two agreeing is the whole point of doing this.

You can also run the address through our IP lookup tool to confirm the country and provider, or use the proxy tester to check the connection responds before you start working in the profile.

Troubleshooting Pay2.house Proxy Errors

The card is declined on the ad platform

Check that you added it from inside the browser profile rather than from your own browser, and that the Pay2.house balance covers the charge plus any hold the platform places on top. A country mismatch between the card and the IP is the other common cause.

The account was flagged anyway

A proxy and a card cover the network and payment signals. They do nothing for a shared fingerprint, a reused phone number, or the same recovery email across accounts. Those are the next places to look.

I have lost track of which card belongs to which profile

Name each card after the profile it belongs to at the moment you issue it. An unlabelled set becomes very hard to untangle once you are past a dozen accounts, and guessing wrong means paying for one account from another account card.

Still getting blocked once everything connects? That is usually an IP reputation problem rather than a setup problem, and our guide on avoiding IP bans covers what to change.

Pay2.house Proxy Setup FAQ

Does Pay2.house need a proxy to work?

No. Pay2.house has no proxy settings and does not route your traffic. The proxy belongs in the browser profile you use the card in, not in Pay2.house itself. That is why this page is about running the two together rather than about configuring one inside the other.

Why not use one card for every account?

Because the payment method is one of the clearest links a platform has between accounts. You can isolate the IP and the fingerprint perfectly and still be connected by a shared card. Issuing one per profile is the entire reason to use virtual cards rather than your own.

Which proxy type suits advertising accounts?

Static residential for accounts you intend to keep, since the IP stays the same and the account does not appear to move between visits. Rotating residential suits research and ad verification, where a fresh IP on each request is the advantage rather than a problem.

Does the card country need to match the proxy country?

It is a good habit. A card issued in one country and used from an IP in another is a mismatch a platform can see. Pay2.house issues BINs across several countries, so you can usually pick one that lines up with the location you are proxying from.