Find invoices and handle payment issues

Find the account's invoice list

Open Billing → Invoices and wait for the records to load. The list belongs to the signed-in account, so check the account email if a payment you expect is absent. A terminal subscription and a separately billed API subscription can produce different billing records. No invoices yet is different from a failed invoice-list request: the first is an empty result, while the second means the service could not establish the list. Preserve the error when the list is unavailable instead of treating it as proof that no billing activity exists.

Use the hosted and download actions

Inspect the available invoice entry and use its hosted or download action to view the provider's payment record. Match the reference, date, amount, currency and status to the action you are investigating. A plan-card price is an offer for a product and interval, while an invoice can include the actual period, proration or other provider billing details. Keep the invoice reference when contacting support. Avoid sharing a private hosted invoice or payment URL publicly, because the reference and safe visible fields usually provide sufficient context.

Distinguish payment states

Past due, payment action required and Billing unavailable describe different situations. Past due concerns an outstanding payment state. Action required can mean the provider needs you to complete an additional payment step. Billing unavailable means OrderMap could not read or perform a billing operation and does not itself establish a failed card payment. A provider-not-configured or price-not-configured message means that requested application action cannot currently be completed. Pressing the button in that state is not evidence that your card was charged.

1. Open Billing → Invoices and identify the relevant record.
2. Read its reference, amount, date and provider status.
3. Compare that record with the current subscription summary and its action message.

Update details through Manage in Stripe

Use Manage in Stripe to update payment details or complete the supported payment action. Enter card information only in the appropriate hosted provider flow, then finish its confirmation steps. Returning to the application without completing the provider action does not resolve the outstanding requirement. Afterward refresh Billing and the invoice list to inspect the saved result. A browser navigation success means the page opened; it does not prove payment acceptance, invoice settlement or that an entitlement projection has already incorporated the provider event.

Check access separately from the payment screen

A payment flow can finish before the application receives or reconciles its provider update. Check the current subscription status and displayed access date after refreshing rather than relying on an old tool screen. Payment-dependent plan changes wait for payment confirmation. A canceled-at-period-end subscription can still show access until its saved end. If a tool remains unavailable, include its exact access error with the billing record; provider dataset availability and retained history are separate boundaries that a settled invoice does not automatically repair.

Avoid ambiguous duplicate attempts

If an action is still processing or a network failure obscured its outcome, inspect Billing and the relevant provider record before starting another independent checkout. A queued or submitted operation can have committed even when its browser response was lost. Repeatedly opening new payment flows makes it harder to identify which transaction corresponds to your intended purchase. Keep the approximate action time and intended plan, and use the same saved record to investigate. An invoice reference and current state are more useful than a screenshot of a spinner alone.

Prepare a safe payment support report

Include the account identity, invoice reference, intended product and billing interval, approximate time with time zone, safe amount and exact visible status or error. Explain whether you were subscribing, changing a plan, updating payment details or canceling. Do not send full card numbers, security codes, bank credentials, authentication tokens or private payment links. Support can investigate the application and provider state without those secrets. Configured Stripe keys, a published price catalog or automated provider-fake tests do not establish that a particular real customer payment succeeded; use the actual record for that conclusion.