Skip to main content
Payment amounts are decided by Arcus and Stripe The portal may show an amount field or balance, but Arcus and Stripe determine the real payable amount, payment intent, and final result. Customers cannot make a paid invoice payable again by editing the browser.

​
Open Portal Payments

Customers open Payments from the portal sidebar. The page shows account balance, payment count, saved payment method summary, and payment history with method, date, amount, and status.
Customer portal Payments page with account balance, payments made, saved payment method summary, and payment history rows

​
Make A Payment

Customers can start a payment when portal payments are enabled and the seller has a healthy payment connector. Invoice-specific payment links are the cleanest path because they carry the record and amount context into the payment flow.
Customer portal Make a Payment modal with amount field and Continue to Payment button over the Payments page
  • Invoice payment: customer opens a portal invoice or public payment link, then pays the current balance due.
  • Amount review: Arcus checks the current balance before creating the payment request.
  • Stripe entry: card, bank, authentication, and final authorization are handled by Stripe.
  • Success: Arcus records the payment, updates the invoice or order payment state, and refreshes payment history.
  • Failure: the customer should see a payment error and staff should review the invoice, connector health, and Stripe result.
Avoid promising standalone payments for every account If a customer starts from the general Payments page without an invoice or payable balance context, the payment can be blocked. Have them open the invoice, public payment link, or contact staff when they are unsure what balance they are paying.

​
Review Payment Methods

Customers can open Payment Methods to review saved cards and bank accounts. The page shows safe display data such as brand, bank name, last four, card expiration, default badge, and available actions.
Customer portal Payment Methods page with default Visa card, bank account card, Add Payment Method button, Set Default action, and Remove action

​
Current Method Actions

The portal can show actions for adding, setting a default, or removing a method. Exact availability depends on the seller’s payment setup and the current portal capability. Some changes may still require staff help.
  • Add Payment Method: starts secure Stripe setup when the seller has enabled the connector and portal flow.
  • Set Default: chooses which saved method is preferred for future eligible payments when the action is available.
  • Remove: removes a saved method when allowed. Default or in-use methods may be blocked.
  • Bank verification: ACH or bank methods may require verification before use.

​
Payment Method Edge States

StateWhat the customer seesStaff follow-up
Add allowedAdd Payment Method starts a secure Stripe setup flow.Confirm Stripe is connected and the account is correct.
Add unavailableAdd action is hidden or blocked.Check portal payment settings, connector health, and account eligibility.
Default methodMethod has a default badge or appears first.Confirm it is still valid before using it for high-value payments.
Expired cardCard may be visible but should not be charged.Ask customer to add an updated card and remove the old one when allowed.
Bank pending verificationBank method may show pending or may be unavailable for payment.Complete verification or have the customer add a verified method.
Remove blockedCustomer cannot remove a default, pending, or in-use method.Set another default first, finish pending payment work, or remove it from staff tools if policy allows.
Payment failedPayment history shows failed or the checkout flow reports an error.Review failure reason, Stripe result, invoice balance, and whether a different method is needed.
Use the public payment link for one-off payment When the customer only needs to pay one invoice or order, send the public payment link. When they need history, saved methods, or broader account review, use portal login.

​
Staff Checklist

  1. Confirm Stripe is connected and healthy before directing customers to portal payments.
  2. Confirm the invoice or order has an open balance.
  3. Confirm the customer is logged into the correct account.
  4. Use public payment links for simple one-off payment requests.
  5. Review Stripe, Arcus payment history, invoice status, and account payment methods when a customer reports a failed payment.

​
Common Blocks

  • Payment button is missing: the invoice may be paid, voided, not customer-visible, or portal payments may be disabled.
  • Amount is zero: open the invoice or public payment link instead of starting from the general Payments page.
  • Connector unavailable: Stripe is not connected, not configured for this entity, or temporarily failing.
  • Card authentication fails: customer may need to complete bank/card authentication or use a different method.
  • ACH or bank method pending: bank verification or settlement may take additional business days.
  • Cannot remove a method: default, pending, or in-use methods may need staff assistance.
  • Wrong balance shown: refresh the invoice and payment history, then review recent payments, credits, refunds, and voids.

Public Order, Payment, and Quote Links

Use tokenized public links for customer order view, payment, shipment tracking, and quote approval.

Customer Portal Overview

Understand portal login, dashboard, customer navigation, setup requirements, and account-scoped visibility.

Portal Invoices and Shipments

Help customers review invoice balances, pay eligible invoices, download PDFs, and track shipments from the portal.

Invoice Management

Find, create, post, send, pay, correct, and void customer invoices.

Record Customer Payments

Record cash, card, ACH, check, wire, external, terms, or credit payments.

Stripe Payments

Configure Stripe keys, webhooks, payment workflows, saved methods, reconcile, payouts, and disputes.