Lead with the offer first
Use the pilot-offer page or PDF before the invoice so the payment ask never arrives without context.
Invoice and receipt system
The payment touchpoint should look as disciplined as the pitch and the product.
Use one branded billing language from pilot offer to invoice to receipt.
These specimen assets keep the first paid pilot from drifting into a generic payment experience. They are designed to align with the live site, the founding pilot offer, and the safe-claims rules already built into RebateOps.
Downloadables
Use these as the visual reference for live payment touchpoints.
Invoice specimen
Download the invoice format PDF
Shows the founding pilot scope, payment posture, and safe billing language in one branded layout.
Receipt specimen
Download the receipt format PDF
Shows how the paid pilot confirmation should feel after Stripe payment clears.
Billing explainer
Open the live payment page
Use the public billing surface when you need to explain how RebateOps handles the first paid pilot.
Offer alignment
Keep the pilot offer in sync
The invoice should never introduce a scope or promise that the live offer page does not already establish.
Usage rules
How to keep live billing aligned with the brand.
Bill for workflow support
Anchor the invoice on packet readiness, missing-item chase, and office operating help, not risky outcomes.
Keep the same identity
Use `hello@rebateops.co`, `rebateops.co`, and the same logo lockup across Stripe, receipts, and email follow-up.
Do not widen the claims
Payment does not change the safe-claims rule. Avoid guaranteed approval, guaranteed timing, or autonomous filing language.