Connect your payment flow
Honor the customer’s billing policy without coupling your experience to one checkout model.
On this page
Billing policy decides when work can begin
Pay-before-work customers must satisfy the initial payment gate. Invoice-later customers follow their configured terms.
The collection mechanism does not change this rule. Recording a payment manually is not a way around a prepaid policy.
Use configured Stripe checkout
Create a checkout session against the order’s prepared invoice. The adapter returns the supported checkout configuration for your UI.
An invoice can still be preparing after order creation. Follow the returned state rather than creating another order. A browser return URL is not payment confirmation; signed provider settlement is authoritative.
Record an external settlement
An approved payments:record profile can record a payment collected in the tenant’s system. Supply amount, currency, method, settlement time, and a stable external payment reference.
Wincora validates the invoice balance and duplicates. This is an asserted external settlement, not a payment independently verified through Wincora’s provider account. Stripe payments must use the provider flow.
Separate adjustments from cash movement
Invoices, credit notes, refund requests, approvals, and completed refunds are distinct resources. Cancellation may require accounting follow-up.
Read financial amounts by currency. Only completed cash refunds reduce collected cash; an unresolved refund remains exposure.
Payments reference