How an engagement runs.

What you're buying

You're paying for payment cloaking on your store, built by hand. Not a plugin. Not a SaaS subscription. Not a dashboard with a login. You pay, I configure your stack, your store starts processing under the cloaked setup, you keep selling.

The deliverable is your store running cleanly through your payment processor under the cloaked arrangement. Stripe is the primary use case I see, but the same approach works elsewhere. The pricing tiers on the landing page describe the scope of work. Final quote happens after a short Telegram conversation about your specific stack and vertical.

What I need from you to start

To quote the engagement, I need a few things on Telegram first:

• The URL of your selling site (or a description if it isn't public yet).
• What stack it runs on. WooCommerce, Shopify, custom Next.js, custom PHP, headless, whatever.
• Your vertical. Be honest about it. I have probably seen it.
• Your payment processor history. Which processor you're on or want to be on, whether you've been banned before, whether you have a usable account already, or whether you're starting clean. Stripe is the most common case I see, but this is the same conversation regardless.
• Whether you want Basic, Standard, or Custom scope. If you aren't sure, I will help you figure it out.

Once we have a quote you accept, kickoff needs the access for your stack. That usually means store admin login, hosting credentials, and SSH or panel access if relevant. The exact list depends on what you run and gets confirmed before deposit.

Engagement flow

1. Scope and quote on Telegram. We talk through your store, stack, vertical, and processor history. I confirm the scope and quote a number. Usually under 30 minutes of back and forth.
2. Deposit and access. 50% deposit on Standard and Custom, full payment on Basic. Crypto is preferred. Once payment lands, you grant the access I confirmed in step one.
3. Setup work. I configure the cloaking on your stack. The exact work depends on what you run. Specifics are part of what you pay for.
4. Test charges. Before handoff, I run real test charges end to end. I verify they settle the way they should, that the buyer experience on your selling site is clean, and that the processor-side view looks right.
5. Handoff. I write up what was changed, where, and what to watch for. I walk you through it on Telegram. Final payment (for Standard and Custom) settles on handoff.
6. Post-delivery support. 30 days of Telegram support for questions, small adjustments, or review-response work if your processor sends an email.

Typical engagement is 3 to 5 days from deposit to handoff. Basic can move in 1 to 2 days when you have everything in hand. Custom takes longer because the spec conversation is bigger.

What you get on delivery

• Your store processing payments successfully under the cloaked setup.
• A written handoff doc that lists what was changed and where, so you can roll back or audit later.
• Test charges already run and verified.
• 30 days of Telegram support included.
• Optional brief on what triggers processor reviews in your vertical, so you can avoid the obvious tells.

What you don't get

Being explicit here because this comes up:

• No source code. The configuration of your stack is yours, the methodology is mine.
• No portable plugin or package. Nothing you can lift off your store and install elsewhere without paying for another engagement.
• No ongoing access on my side after handoff. Once delivery is done, your access is your access.
• No shared infrastructure. Your setup runs on your stack. There's no central server you depend on and no kill switch I hold.
• No method disclosure. The specific techniques used to harden the setup against review are part of what you pay for and stay between me and the engagement.

What to avoid post-delivery

Processors run continuous risk scoring on every merchant. The cloaking buys you a clean view at the start. Your behavior on the account is what determines how long it lasts.

Things processors watch:

• Sudden volume spikes. Going from $0 to $50k in week one will trigger a review regardless of how clean the setup is. Ramp.
• Refund ratios. High refund volume reads as quality problems or evasion. Keep refunds below 5% if you can.
• Chargeback ratios. Above 1% gets you on the radar. Above 2% gets the account frozen. Disputes are a hard line.
• Customer complaints filed directly with your processor. Even one or two can trigger a manual review.
• Velocity changes. Doubling daily volume month over month with nothing on the public side to explain it.
• Mismatched billing data. If shipping is to one country and the card is from another consistently, that's a signal.

None of this is unique to a cloaked setup. It's what any processor watches on any merchant. The handoff doc you get will cover the version of this list that's specific to your vertical.

Retainers and maintenance

After the 30 days of included support ends, you have options:

• Per-incident repair. Your processor sends a review email or asks for documentation, you message me, I scope a quick engagement. Fair pricing depending on what's needed.
• Monthly retainer. If you want me on standby for whatever comes up, retainers are available. Pricing depends on volume and how active your account is. We scope it on Telegram.
• Just message me when something happens. No retainer, no contract. Most people do this. You DM me with a problem, I quote the fix, we go.

Refund policy

No refunds once work has started. The deposit is fully refundable up to kickoff if scope turns out to be wrong for what you actually need and we cancel before I touch anything. Once access is granted and setup work begins, the deposit is non-refundable.

If something goes wrong on my end during the engagement (I can't deliver what was scoped), you get a full refund and we walk away. This has not happened, but it's the deal.

How to start

DM me on Telegram with the things from the "What I need from you" section above. I usually respond within a few hours.

Message @lucimornens