> ## Documentation Index
> Fetch the complete documentation index at: https://docs.arcuserp.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Portal Payments and Payment Methods

> Let customers review payment history, start eligible payments, and review saved payment methods from the customer portal.

<Note>
  **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.
</Note>

## 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.

<Frame caption={"Portal Payments gives customers a customer-safe view of balance, saved method summary, and prior payments."}>
  <img src="https://mintcdn.com/arcuserp/MrJkb10V6EpIZu0o/images/support/screenshots/customer-portal/customer-portal-payments.png?fit=max&auto=format&n=MrJkb10V6EpIZu0o&q=85&s=2bed62d1f9b13555857f202a76d2ded2" alt="Customer portal Payments page with account balance, payments made, saved payment method summary, and payment history rows" width="1920" height="1100" data-path="images/support/screenshots/customer-portal/customer-portal-payments.png" />
</Frame>

## 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.

<Frame caption={"The payment modal starts the payment flow. Stripe handles the secure card or bank payment entry after the amount and record context are accepted."}>
  <img src="https://mintcdn.com/arcuserp/MrJkb10V6EpIZu0o/images/support/screenshots/customer-portal/customer-portal-make-payment-modal.png?fit=max&auto=format&n=MrJkb10V6EpIZu0o&q=85&s=6a838c66fb7c64f3a9636ce1fd10e47b" alt="Customer portal Make a Payment modal with amount field and Continue to Payment button over the Payments page" width="1920" height="1100" data-path="images/support/screenshots/customer-portal/customer-portal-make-payment-modal.png" />
</Frame>

* **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.

<Warning>
  **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.
</Warning>

## 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.

<Frame caption={"Payment Methods shows safe display details only. Full card and bank numbers are never shown in the portal."}>
  <img src="https://mintcdn.com/arcuserp/MrJkb10V6EpIZu0o/images/support/screenshots/customer-portal/customer-portal-payment-methods.png?fit=max&auto=format&n=MrJkb10V6EpIZu0o&q=85&s=1c187fcf61f5d221a1b3d3f654ab85ca" alt="Customer portal Payment Methods page with default Visa card, bank account card, Add Payment Method button, Set Default action, and Remove action" width="1920" height="1100" data-path="images/support/screenshots/customer-portal/customer-portal-payment-methods.png" />
</Frame>

## 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

| State                     | What the customer sees                                              | Staff follow-up                                                                                         |
| ------------------------- | ------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------- |
| Add allowed               | Add Payment Method starts a secure Stripe setup flow.               | Confirm Stripe is connected and the account is correct.                                                 |
| Add unavailable           | Add action is hidden or blocked.                                    | Check portal payment settings, connector health, and account eligibility.                               |
| Default method            | Method has a default badge or appears first.                        | Confirm it is still valid before using it for high-value payments.                                      |
| Expired card              | Card may be visible but should not be charged.                      | Ask customer to add an updated card and remove the old one when allowed.                                |
| Bank pending verification | Bank method may show pending or may be unavailable for payment.     | Complete verification or have the customer add a verified method.                                       |
| Remove blocked            | Customer 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 failed            | Payment history shows failed or the checkout flow reports an error. | Review failure reason, Stripe result, invoice balance, and whether a different method is needed.        |

<Tip>
  **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.
</Tip>

## 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.

## Related Articles

<CardGroup cols={2}>
  <Card title="Public Order, Payment, and Quote Links" href="/support/customer-portal/public-links">
    Use tokenized public links for customer order view, payment, shipment tracking, and quote approval.
  </Card>

  <Card title="Customer Portal Overview" href="/support/customer-portal/overview">
    Understand portal login, dashboard, customer navigation, setup requirements, and account-scoped visibility.
  </Card>

  <Card title="Portal Invoices and Shipments" href="/support/customer-portal/invoices-shipments">
    Help customers review invoice balances, pay eligible invoices, download PDFs, and track shipments from the portal.
  </Card>

  <Card title="Invoice Management" href="/support/invoices/management">
    Find, create, post, send, pay, correct, and void customer invoices.
  </Card>

  <Card title="Record Customer Payments" href="/support/orders/record-payment">
    Record cash, card, ACH, check, wire, external, terms, or credit payments.
  </Card>

  <Card title="Stripe Payments" href="/support/integrations/stripe-payments">
    Configure Stripe keys, webhooks, payment workflows, saved methods, reconcile, payouts, and disputes.
  </Card>
</CardGroup>
