Checkout, handoff and safety

The standard path

Official referral link
-> Landing page
-> Package and checkout
-> Stripe payment
-> Customer portal
-> Material readiness
-> Production and QA
-> Customer approval
-> Publish

Keeping the customer inside this path protects attribution, receipts, scope, production records, and commission.

Before checkout

Confirm that the customer:

• understands the proposed package and its limits;
• knows which questions still need AlphaBlue confirmation;
• will pay through the official checkout;
• can provide accurate business details and publishing permission;
• understands that delivery starts after required materials are ready.

After checkout

The customer receives access to the customer portal and follows the material process. The partner can help the owner understand the checklist, but should not take ownership of business accounts or store credentials without an approved need.

Assisted partners receive only the access required for an approved task. Access should be time-bounded and customer-specific.

Safety boundaries

A partner must not:

• collect customer payment or request Stripe credentials;
• edit price, refund, or payment status;
• promise an unapproved feature, discount, date, or result;
• export unrelated customer information;
• accept legal authorization on the customer’s behalf;
• register the customer’s domain, social account, or business asset in the partner’s own name;
• keep passwords in personal notes or chat history.

A clean handoff note

Send AlphaBlue:

• the business name and main contact;
• the customer’s stated problem;
• the use case and package discussed;
• any scope question that remains open;
• the referral link used;
• the customer’s preferred contact channel.

Do not send sensitive credentials in the note.

The final rule

If an action affects payment, legal approval, account ownership, customer privacy, or an unlisted promise, stop and ask AlphaBlue before proceeding.