Payment Gateway Replica Store

[pr0fit]

$100k/month selling blackhat products is risky business but very impressive that you manage to get this type of revenue, you got something going on.

I would personally advise you to have multiple gateways and split volume. Some type of manual verification will eventually happen and depending on your setup, if anything looks off to them it's gonna be a lot of headaches.

Are payouts next day? 100k/month you are averaging around $3k/day. In the perfect world, if you are capable of getting 3 processors and split volume at $1k/day each, this is a very nice numbers processors are comfortable with.

I wrote a thread actually in regards to this exact type of problems I keep seeing here and I am contemplating putting it into action, if I find the right fit.

 

[Celiaaa]

$100k/month selling blackhat products is risky business but very impressive that you manage to get this type of revenue, you got something going on.

I would personally advise you to have multiple gateways and split volume. Some type of manual verification will eventually happen and depending on your setup, if anything looks off to them it's gonna be a lot of headaches.

Are payouts next day? 100k/month you are averaging around $3k/day. In the perfect world, if you are capable of getting 3 processors and split volume at $1k/day each, this is a very nice numbers processors are comfortable with.

I wrote a thread actually in regards to this exact type of problems I keep seeing here and I am contemplating putting it into action, if I find the right fit.

I completely agree with your point about splitting volume across multiple processors. That’s actually very close to the logic behind cloaking, especially when using multi-cloaking setups , with this approach, instead of pushing $3K/day through a single store or gateway, you can distribute it across multiple stores in the background—for example $1K/day on 3 different stores. This helps reduce risk, avoid red flags, and keep everything much more stable long-term.

It’s essentially the same principle you mentioned, but applied at the store and infrastructure level rather than just the payment processors.

Curious to hear your thoughts on that approach.

 

[pr0fit]

I completely agree with your point about splitting volume across multiple processors. That’s actually very close to the logic behind cloaking, especially when using multi-cloaking setups , with this approach, instead of pushing $3K/day through a single store or gateway, you can distribute it across multiple stores in the background—for example $1K/day on 3 different stores. This helps reduce risk, avoid red flags, and keep everything much more stable long-term.

It’s essentially the same principle you mentioned, but applied at the store and infrastructure level rather than just the payment processors.

Curious to hear your thoughts on that approach.

The whole context of "cloaking" is very new to me. I work with merchant acquirers who provide merchant accounts directly from the bank and I create my own custom payment gateways. In doing so, the gateway is fully capable of creating, processing, verifying and capturing a transaction of an amount successfully but filters some of the information that is being given to the merchant processor itself such as website the transactions was made on or product descriptions.

Being very familiar with volume splitting, you do not need multiple stores. You would need 3 different merchant providers with 3 payment gateways installed on the same store. You enable merchant 1 and disable the other 2. Once you reach threshold, you disable merchant 1, enable merchant 2 and continue.

This is only done through woocommerce, I do not use any other platforms.

Again, I really am not familiar with "cloaking" concept. Online payment processing is complex and there is not a lot of information that goes in depth. Payment gateway and merchant accounts are two completely different things. Most people use the service of payment gateways, which is designed to transmit as much information to the processor as possible as well as the highest level of security in order to get paid. So for example, I can create my own gateway, apply for a contract with Bank of America as a reseller of their credit card processing. I now market my gateway as a "payment processor" but in reality, I am just an integration that faciliates the transactions and communicates it to BoA. It's to my benefit that I do the best possible job to ensure every transaction is legit and make it as hard as possible to fraud because if my gateway is not good and is telling the acquirer to process a transaction when it should not, I do not get paid and eventually they will drop me.

I wrote this because from what I understand, we are cloaking payment gateways with other payment gateways. It might work, but to me, this is a "quick fix" and a subpar method to achieve cloaking.

Get a merchant account and then create your own gateway. Problem fixed

 

[Jenbum]

The whole context of "cloaking" is very new to me. I work with merchant acquirers who provide merchant accounts directly from the bank and I create my own custom payment gateways. In doing so, the gateway is fully capable of creating, processing, verifying and capturing a transaction of an amount successfully but filters some of the information that is being given to the merchant processor itself such as website the transactions was made on or product descriptions.

Being very familiar with volume splitting, you do not need multiple stores. You would need 3 different merchant providers with 3 payment gateways installed on the same store. You enable merchant 1 and disable the other 2. Once you reach threshold, you disable merchant 1, enable merchant 2 and continue.

This is only done through woocommerce, I do not use any other platforms.

Again, I really am not familiar with "cloaking" concept. Online payment processing is complex and there is not a lot of information that goes in depth. Payment gateway and merchant accounts are two completely different things. Most people use the service of payment gateways, which is designed to transmit as much information to the processor as possible as well as the highest level of security in order to get paid. So for example, I can create my own gateway, apply for a contract with Bank of America as a reseller of their credit card processing. I now market my gateway as a "payment processor" but in reality, I am just an integration that faciliates the transactions and communicates it to BoA. It's to my benefit that I do the best possible job to ensure every transaction is legit and make it as hard as possible to fraud because if my gateway is not good and is telling the acquirer to process a transaction when it should not, I do not get paid and eventually they will drop me.

I wrote this because from what I understand, we are cloaking payment gateways with other payment gateways. It might work, but to me, this is a "quick fix" and a subpar method to achieve cloaking.

Get a merchant account and then create your own gateway. Problem fixed

Use an orchestrator like paytree.