Stripe Connect allows your organization to connect its Stripe account to Elite Core so customers can securely pay invoices online. Once the connection is configured, Elite Core can use the connected Stripe account as part of the invoice payment workflow while Stripe handles the sensitive payment processing.
This guide explains what Stripe Connect is, how the connection works, how Test Mode differs from Live Mode, how to test invoice payments safely, what happens when a customer pays, and what should be verified before your organization begins accepting real customer payments.
What Is Stripe Connect?
Stripe Connect is the connection between your organization’s Stripe account and Elite Core. It allows Elite Core to use Stripe as the payment processor for supported online Invoice payments without requiring staff to collect or manually handle a customer’s card information.
Elite Core manages the customer, Invoice, payment context, balance, and resulting workflow. Stripe processes the payment itself. This separation is important because sensitive card information should remain inside Stripe’s supported payment experience rather than being stored in Project notes, emails, messages, or other unsecured places.
How Stripe Connect Works
At a high level, the payment flow is straightforward. Elite Core creates or displays the Invoice, the customer opens the supported payment experience, Stripe processes the payment, and Elite Core receives the result so the Invoice and payment workflow can be updated.
A useful way to think about the flow is: Elite Core Invoice → Customer Opens Payment → Stripe Processes Payment → Payment Succeeds → Elite Core Updates the Invoice and Payment State.
Suggested Visual
Add a simple horizontal flow diagram showing an Elite Core Invoice on the left, a customer payment page in the middle, Stripe processing next, and an updated paid Invoice in Elite Core on the right.
Connecting Stripe to Elite Core
Open the Stripe settings area available to your organization in Elite Core. Depending on your role and permissions, this may appear inside organization settings, financial configuration, or a payment configuration area.
Choose the option to connect Stripe. Elite Core will redirect you into the Stripe Connect onboarding process, where you sign in to the Stripe account that should receive your organization’s payments. Complete the business, banking, identity, ownership, or verification information requested by Stripe, confirm the connection, and then return to Elite Core.
After returning to Elite Core, verify that the Stripe connection shows as active and that the account belongs to the correct organization. A successful connection does not always mean the Stripe account is immediately ready for live transactions. Stripe may still require additional information before the account is fully enabled.
If Stripe requests additional verification, complete those requirements directly through Stripe before relying on the account for production payments.
Test Mode and Live Mode
One of the most important parts of Stripe setup is understanding the difference between Test Mode and Live Mode.
Test Mode is used for setup, training, development, quality assurance, and payment testing. No real customer money should move when a transaction is correctly processed in Stripe Test Mode. Live Mode is the production environment and processes real customer cards, real charges, and real money.
Users should always complete the full Invoice payment workflow in Test Mode before accepting real customer payments.
Testing a Payment Safely
Never use a real customer credit card while testing Stripe. Use Stripe’s test payment information instead.
For a normal successful test payment, use the card number 4242 4242 4242 4242. Use any valid future expiry date, such as 12/30, and a valid test CVC such as 123. Enter a valid-looking postal or ZIP code if the payment form requires one.
When testing an Elite Core Invoice, first confirm Stripe is operating in Test Mode. Open the Invoice or payment experience, choose the card-payment option, enter the 4242 test card, provide a future expiry date and test CVC, complete any required billing information, and submit the payment.
After the payment succeeds, return to Elite Core and verify that the expected Invoice and payment information has updated. The 4242 card simulates a successful transaction. When it is used correctly in Test Mode, no real card is charged and no real customer funds are collected.
What to Test Before Going Live
Before enabling real payments, run at least one complete controlled Invoice-payment test from beginning to end. Confirm that Stripe shows as connected and that the correct organization or Stripe account is attached. Open an Invoice and confirm that the expected payment option appears. Complete a payment with the 4242 test card and verify that the successful-payment confirmation appears.
Then return to Elite Core and confirm that the transaction is recognized, that the Invoice or payment status is updated as expected, and that the amount paid matches the amount that was intended. If the Invoice contains a prior deposit, verify that the deposit is correctly reflected before payment. If partial-payment or selected-Invoice workflows are being used, test those scenarios as well.
Elite Core includes specific payment-success handling, so part of the test should include what the customer sees immediately after payment and what staff see in the Invoice afterward.
Live Mode
Live Mode processes real customer payments. Once the Stripe account is being used in Live Mode, customers should use their actual credit or debit card information and real charges will be created.
Real money moves through Stripe in Live Mode, Stripe processing fees may apply, and payouts ultimately follow the connected Stripe account’s payout configuration. Live Mode should only be used after the account, banking information, customer-payment flow, Invoice balances, and payment-status behavior have all been reviewed.
Before Switching to Live Mode
Confirm that the correct business Stripe account is connected. Do not connect a personal Stripe account, a development account, the wrong company account, or an account belonging to another organization.
Confirm that Stripe has completed any required verification. Depending on the account, Stripe may request business information, business address information, ownership details, identity verification, banking details, or tax and registration information.
Verify that the correct bank account is configured for payouts. Complete at least one successful Test Mode payment and confirm that the payment flows correctly through Elite Core. Finally, verify that the amount shown to the customer matches the actual Invoice balance before accepting real payments.
Suggested Visual
Add a two-column comparison graphic titled Test Mode vs. Live Mode. The Test Mode side should show simulated payments, the 4242 test card, training and QA, and no real money. The Live Mode side should show real customer cards, real payments, production use, and real payouts.
What Happens When a Customer Pays an Invoice?
When a customer completes an online Invoice payment, Stripe processes the transaction. The customer opens the Invoice or payment experience, chooses what they want to pay where that workflow is supported, enters their payment information, and submits the transaction.
Stripe returns the payment result to the supported Elite Core workflow. Elite Core then displays the appropriate result and associates the successful payment with the Invoice and payment context so the Invoice can reflect its updated payment state.
Elite Core also supports customer-selected Invoice payments. In that workflow, customers can choose an Invoice or supported set of Invoices to pay rather than Stripe acting as a generic standalone checkout page.
Stripe and Multiple Invoices
Where enabled, a customer may be able to select which outstanding Invoice or Invoices they want to pay. This creates a payment experience closer to an Accounts Receivable portal.
For example, a customer might have Invoice A with $500 outstanding, Invoice B with $750 outstanding, and Invoice C already paid. The customer should only be presented with the applicable outstanding payment options. After testing a multi-Invoice transaction, verify the payment allocation carefully so each Invoice reflects the correct result.
Stripe and Deposits
Deposits can change the amount a customer should be asked to pay. Elite Core contains dedicated Invoice deposit logic, so users should verify that previously received deposits have been applied correctly before directing the customer to Stripe.
For example, if the Sales Order or Invoice total is $5,000 and the customer already paid a $2,000 deposit, the remaining balance should be $3,000. The customer should not be charged the original $5,000 if the deposit has already been correctly recorded and applied.
Always review the Invoice balance before sending the customer into the online payment flow.
Suggested Visual
Add a balance-reduction graphic showing $5,000 Invoice Total − $2,000 Deposit Paid = $3,000 Remaining Balance, followed by the $3,000 balance moving into the Stripe payment step.
Stripe Payment Security
Customers should enter payment information directly into the supported Stripe payment interface. Staff should never ask customers to send full card numbers through email, Slack, Teams, text messages, Project notes, Sales Order notes, Artwork notes, or other unsecured communications.
Sensitive payment details belong inside Stripe’s payment flow. Keeping card information out of general communication and Project records reduces risk and keeps the payment process within the system designed to handle it.
Common Questions
Can I use a real credit card in Test Mode?
Use Stripe test payment credentials instead. For a normal successful test, use 4242 4242 4242 4242, a future expiry date, and a test CVC such as 123.
Will the 4242 card actually charge money?
Not when it is used correctly in Stripe Test Mode. The card number is intended to simulate a successful Stripe transaction.
Can I use 4242 in Live Mode?
No. Stripe test card numbers are intended for the testing environment. Live Mode requires a legitimate payment method.
How do I know we are ready for Live Mode?
The correct Stripe account should be connected, Stripe onboarding and verification should be complete, banking information should be confirmed, Test Mode payments should work successfully, Elite Core Invoice updates should be verified, deposits and balances should be correct, and the full customer payment experience should have been reviewed.
Does connecting Stripe automatically mean we are ready for real payments?
Not necessarily. A connected Stripe account may still require additional verification or configuration. Always confirm that the account is fully enabled and complete a controlled Test Mode verification before relying on it for customer transactions.
Recommended Go-Live Test
Before announcing online payments to customers, create a controlled Invoice and run the complete process internally in Test Mode. Open the Invoice, enter 4242 4242 4242 4242, use a future expiry date and test CVC, complete the payment, and confirm that Elite Core reflects the successful result.
The full test should behave as: Invoice → Payment Page → 4242 Test Card → Successful Payment → Elite Core Updated.
Once that entire flow operates correctly, review the Stripe connection one final time and use the appropriate Live Mode configuration for real customer transactions.
Key Takeaway
Test Mode is for simulated payments, setup, training, and verification. Use Stripe test credentials such as 4242 4242 4242 4242 to simulate a successful payment without moving real money.
Live Mode is for real customer transactions. Customers use legitimate payment methods and real funds are processed through the connected Stripe account.
Always test the complete Invoice payment workflow before accepting live customer payments.
