Explain what the customer is buying
Describe your products or services, pricing, customer markets and delivery model. Explain when the customer pays and when they receive what they ordered. If you sell subscriptions, describe the billing cadence, trial or introductory offer, renewal terms and cancellation process.
Include your public website if it is ready. A pre-launch merchant can explain the intended journey and what remains unfinished. Do not imply an established processing history if you do not have one.
Separate forecasts from actual activity
New merchants should label expected order volume and average order value as estimates. Established merchants can describe current activity and the reason for evaluating another arrangement, such as a platform change or a need to review supported payment operations.
If a partner later requests processing statements or identity documents, use the submission channel it specifies. A general contact form is not the place for bank statements, identity documents, payment credentials or shopper records.
Describe the operating controls
Be ready to explain fulfillment, customer support, returns, refunds and recurring cancellation. Identify who handles disputes and how customer requests are recorded. The goal is an accurate account of your operation, not a claim that a checklist guarantees acceptance.
- Business location and intended customer countries
- Platform, website status and supported integration requirements
- One-time versus recurring payments
- Expected or actual volume and average order value
- Delivery timelines and refund or cancellation process
- Existing gateway requirements and the reason for seeking assistance
Review commercial terms before committing
Ask the partner to explain processing fees, other charges, reserves, settlement timing and any volume or activity restrictions. Clarify which currencies, business activities and customer markets are covered. Do not assume the same terms apply across providers.
Approval, pricing and availability remain partner decisions. Rebillora’s software pricing is separate from payment processing fees, and a demo or software account does not constitute processing approval.
Connect approval with the launch workflow
An approved processing arrangement still needs an appropriate technical setup. Confirm gateway compatibility, checkout behavior, routing needs and subscription requirements before directing live traffic. If you already have subscriptions, assess payment-method portability and migration constraints explicitly.
Rebillora can help explore processing options through partners and review the CRM workflow around them. Choose CRM, processing assistance or both in the demo form, then use the conversation to identify the next concrete steps.