Skip to main content

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.

​
Open Stripe Configuration

  1. Open Integrations.
  2. Find the Stripe card.
  3. Click Connect or Configure.
  4. Confirm the environment is Sandbox or Production.
  5. Enter or rotate the Stripe secret key and publishable key when needed.
  6. Configure webhook signing if the entity uses Stripe webhooks.
  7. Save, test the connection, then test a small payment workflow.
Configure Stripe modal showing environment selection, masked credentials, webhook setup, reconnect, test, reconcile, and save actions
Production Stripe can charge real customers Production mode should be changed only by an admin who owns the Stripe account and knows which entity is being configured. Use sandbox mode for dev and testing workflows.

​
Credential Fields

  • Secret Key: required server-side Stripe credential.
  • Publishable Key: used for secure client-side card collection.
  • Webhook Signing Secret: used to verify webhook events when webhooks are configured.
Saved credentials stay masked If a credential is already saved, Arcus shows a masked field. Use Reconnect when you need to paste a new key or rotate credentials.

​
Stripe Webhooks

Webhooks let Stripe notify Arcus about real-time payment events. The Stripe configuration modal shows the webhook URL, required events, current receipt status, and signing-secret status.

  • Use the webhook URL shown in Arcus when creating the endpoint in Stripe.
  • Select the events Arcus lists in the setup guide.
  • Paste the signing secret into Arcus after Stripe reveals it.
  • Use the test webhook action when the secret is saved.
Use Reconcile Stripe data after credential repair If payment method references or customer references become stale after a Stripe account change, use the reconcile action to sweep cached Stripe references and clear stale ones.

​
Workflows Affected By Stripe

  • Record Customer Payments: card and ACH processing depends on Stripe readiness.
  • Saved Payment Methods: secure card and bank entry uses Stripe-hosted fields.
  • Payment Holds: ACH clearance, disputes, failures, and capture rules can affect fulfillment.
  • Payouts: Stripe payout context can feed accounting reconciliation workflows.
  • Disputes: chargebacks and evidence deadlines are monitored through platform dispute workflows.

​
Common Blocks

  • Card fields do not load: check the publishable key, browser blockers, and Stripe availability.
  • Payment fails immediately: confirm the secret key, environment, account status, and test card or live card context.
  • Webhook shows no activity: confirm the endpoint URL, event selection, signing secret, and Stripe test webhook result.
  • Saved payment method is stale: reconcile Stripe data and re-save the customer’s payment method if needed.
  • ACH timing is confusing: review payment settings and order holds before releasing fulfillment.

Connector Dashboard

Review connector mode, health, masked credentials, tests, logs, sync dashboard, and safe reconnect steps.

Record Customer Payments

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

Portal Payments and Payment Methods

Review customer portal payment history, payment starts, saved methods, and common payment blocks.

Payment Methods

Save cards and bank accounts for future customer payments.

Payments and Checks Settings

Configure payment terms, payment automation, processing fees, AP check printing, and deposit slip layout.

Marketplace Payouts

Review Shopify, Amazon, eBay, and Stripe payouts, clearing balances, fees, and needs-review items.