Payments, invoices, fees and carrier earnings

Give a safe invoice, booking or payment reference and the displayed status. Never send full card numbers, security codes, passwords, recovery codes or banking login details in chat. Use the payment provider’s authorised controls for payment credentials.

Check the invoice/payment status after the provider flow and any required confirmation. A submitted card form, loading screen, offer acceptance or successful-looking screenshot is not conclusive. If the provider charged you but the platform still shows pending, contact finance support with the reference.

Refresh the owned payment/invoice status and read the provider message before retrying. Avoid repeated blind submissions that could create confusion. If the outcome is uncertain, ask human finance support to reconcile the reference. The assistant cannot confirm a bank charge it cannot access.

Use the current published fee terms and the financial breakdown shown for your booking. Rates, promotions, VAT treatment and account terms can vary with configuration. This help pack does not promise a universal percentage or tax outcome; ask finance support about an unclear charge before confirming.

Do not treat the platform as a bank escrow service. The reviewed checkout uses a payment-provider integration and its status/reconciliation process. Read the current published payment terms for your booking, including any holds, refund conditions or operational review.

In Android 1.0.5 source, open Home → Earnings & statements for job earnings, or All tools → Earnings. All tools → Statements opens period statements. Job earnings and statement totals are not the available Stripe cash-out balance. Open Cash-out & payouts to refresh that balance separately. The Android source still requires compilation and device testing before distribution.

The updated Android 1.0.5 source adds Cash-out & payouts on carrier Home and under All tools → Finance. On the updated web driver-earnings page, use Cash-out & payouts above the earnings records. Initial Stripe Express setup, verified account linking and enabling cash-out are web-admin tasks. When the account is ready and has available EUR funds, enter an amount, select its payment source and confirm a standard payout to your default Stripe bank destination. Bank details are managed in a secure Stripe-hosted screen. If confirmation is interrupted, check or retry the same request reference; do not start another. A submitted payout is not proof of bank receipt. Older installed Android builds do not have this new screen.

Refresh Cash-out & payouts to see Stripe’s current payout status, reference and estimated arrival date. The estimate is not a guarantee. Pending, in transit, paid, failed and cancelled are different outcomes. If a request remains uncertain, preserve its reference and contact finance support; an old ambiguous request requires reconciliation rather than a new cash-out. This update supports standard EUR payouts; it does not promise instant cash-out.

No. It can explain the current published procedure and help collect safe references for human follow-up. Refund decisions, payout releases, financial corrections and disputes require authorised review and the actual payment/finance process.

The Android source candidate adds Open invoice & secure payment inside invoice details, and All tools → Secure invoices & payments. These open the responsive Logistics web invoice/payment flow in an in-app browser. Sign in with the same Printuvi account if prompted; the browser login is separate from the native session. The server still checks invoice ownership, payable status and Stripe configuration. This is a web checkout reached from the app, not a newly implemented native card-entry form, and it requires device and Stripe test-mode verification before release.