Configure the business first
Confirm the issuing company, invoice numbering, currency and approval policy. Then configure the payment connection for that installation using the administrator's own merchant credentials.
The included product workflows support configured Stripe and eWAY invoice payments and payment-request links. eWAY collects AUD using the saved conversion quote. A browser's success page alone is not evidence that an invoice was settled.
Verify before accepting payments
Complete the gateway's test procedure and confirm a verified receipt and correct invoice allocation. Review the gateway's currency and merchant requirements. Do not switch to live payments just because configuration was saved.
Configure workers once
The release includes bin/process-mail.php for outgoing mail and modules/customer-payment-requests/bin/worker.php --run for bounded payment-request reconciliation. Follow the supplied operations guide to schedule each job with the installation's PHP executable.
These workers can send mail or contact configured providers. Avoid duplicate jobs. Review outstanding requests and reconcile provider outcomes before attempting another charge.
Keep the two payment systems separate
Payments on Emaila Orbit purchase your software entitlement. Payment gateways configured inside your Accounts installation collect payments for your own invoices. They use separate credentials, records and verification flows. Configuring one does not configure or settle the other.

