Integrations · Business tools
Connect your agency's own Stripe account with Stripe Connect. Clients pay their invoices from the portal through Stripe Checkout, and the money goes straight to your Stripe account — Agency Pilot never holds it.
Invoices are numbered and tracked per client, show in the client's portal with a Pay now button, and update when Stripe confirms the payment. Overdue invoices surface in Mission Control so nobody has to chase them from a spreadsheet.
Settings → Payments → Disconnect, or remove Agency Pilot from your Stripe dashboard's connected platforms.
Start a 14-day trial with 300 credits and connect it from Settings in a couple of minutes.
The Stripe integration for agency invoices connects your agency’s own Stripe account to the invoice payment experience in the client portal. Before starting, confirm which business should receive the money and who is authorized to connect that account. This is especially important when an agency operates more than one legal business or works with separate client-facing brands. The account selected for payment collection should match the agency’s intended billing arrangement, rather than whichever Stripe login happens to be open.
The product describes using Stripe Connect from Settings → Payments, with clients paying through Stripe Checkout. Money goes to the connected Stripe account; Agency Pilot does not hold it. Keep the receiving account identity in your internal billing setup notes so that another administrator can understand the arrangement without copying private credentials. The connection gives clients a payment route. It does not decide the commercial terms, approve an invoice or establish what the client has agreed to buy.
Before sending a payable invoice, confirm the client, the description of the work and the amount against the agreement you intend to bill. Make the invoice understandable to the person who will approve payment, who may differ from the day-to-day marketing contact. If the client needs a reference or an internal approval step, resolve that before asking them to pay. A clear invoice and a visible payment action work together; checkout cannot repair an ambiguous or disputed scope.
Illustrative example: an agency completing an agreed website milestone could create the relevant client invoice and make it available in the portal. The account manager confirms the milestone has been accepted, the billing contact reviews the invoice and the client pays through the displayed Stripe route. The agency then verifies the payment state after confirmation. This is an example of an operating process, not a promise that connecting Stripe automatically approves milestones or resolves a disagreement about delivered work.
The described invoice flow updates when Stripe confirms payment. That distinction matters when someone reports that they clicked Pay now but the agency has not yet established the outcome. Inspect the actual invoice state and the relevant provider payment information before treating the payment as complete or asking the client to retry. Preserve the invoice identifier and timing so the billing person can compare the same transaction on both sides.
Avoid using a client’s return to a page or a screenshot of a button click as the only evidence of payment. The useful question is whether the expected invoice has the expected confirmed result. If the state is unclear, investigate that uncertainty before creating another charge. The integration can provide the payment path and confirmation-driven status, while the agency still needs a careful process for answering client billing questions and correcting a mistaken invoice.
The product supports saving a card with the client’s consent and charging a saved card. Treat those as explicit payment workflow decisions. Explain the intended use to the client and keep the agency’s record of the applicable arrangement. The ability to charge a stored payment method does not, by itself, mean that every future amount has been agreed. Confirm the correct client, invoice and authority for a charge before taking the action.
For ongoing work, document what the client expects to be billed and who handles a change in scope or amount. Do not describe a saved card as proof that an unattended subscription schedule has been configured; the source describes saving and charging a card, which is a narrower capability. When the client relationship changes, review whether the existing payment arrangement still matches the work. Keep payment credentials and full card details out of ordinary client notes, support messages and handover documents.
The client portal makes invoices visible to the client, and overdue invoices surface in Mission Control according to the product description. Agree how the agency uses that visibility. An overdue indicator can prompt someone to review the situation, but it does not establish why the invoice remains unpaid. The billing person may already know about a correction, an approval dependency or a commercial discussion. Coordinate with that person before sending a reminder or changing service delivery.
Keep the delivery conversation focused on the agreed next action. Record which invoice is being discussed, who is responsible for resolving the question and whether an adjustment or explanation is needed. A team should not infer a client’s intent from a payment status alone. The advantage of connected billing is shared context: the account manager can identify the relevant invoice while the authorized billing person verifies the financial result through the proper records.
Stripe’s standard fees apply to the client-payment arrangement described here. The agency should review the relevant provider records for its actual charges rather than assume a universal fee or a particular settlement time. Keep the distinction between the client invoice amount, the payment result and the provider’s account activity clear in your accounting process. This guide describes the integration workflow; it does not replace the agency’s existing reconciliation responsibilities or its accountant’s treatment of the transaction.
Before changing or disconnecting the receiving account, list unpaid invoices and any saved-card workflow the team expects to use. Agree how clients will pay future invoices and how questions about earlier payments will be investigated. The source describes disconnecting from Agency Pilot payment settings or removing Agency Pilot from the connected platforms in Stripe. Do not treat that action as cancellation of the separate Stripe account, a refund of past payments or closure of every outstanding invoice. Verify the intended replacement process before relying on it.
Your agency connects its own Stripe account, and the product says client payments go directly to that account rather than being held by Agency Pilot. Confirm the intended receiving business before connecting, especially if your administrators can access multiple accounts. Keep that identity in the billing handover record. The ability to sign in to an account is not a substitute for confirming that it is the correct destination for the agency’s invoices.
The documented route is Settings → Payments → Connect with Stripe, where the authorized agency person signs in to their own account. Use that dedicated connection flow. Before proceeding, agree who owns the billing setup and who will verify its result. Keep ordinary project notes focused on the account identity and workflow rather than copying sensitive payment credentials into a general team document.
The product describes invoices in the client portal with a Pay now action that uses Stripe Checkout. Make sure the client knows which invoice and scope they are paying for, and that the correct billing contact can review it. A visible payment action reduces the need for an external payment conversation, but it does not resolve an incorrect amount, unclear description or missing approval from the client’s own team.
Use the confirmed payment state, not merely the fact that the client opened checkout or clicked a button. The documented workflow updates the invoice when Stripe confirms payment. If a client reports payment while the invoice state is unclear, compare the invoice identifier, time and provider record before asking for another attempt. This separates a genuine unpaid invoice from a status question that needs investigation.
The source states that money goes to the agency’s own Stripe account and Agency Pilot does not hold it. Review the provider account for the details of its payment and balance activity. Do not infer a promised payout schedule from that statement; the receiving account and provider processes still matter. Keep the account owner and billing team responsible for checking the financial records relevant to the agency.
The product supports saving a card with the client’s consent. Explain the intended purpose and keep the agency’s record of the arrangement. Saving a payment method should not be presented as automatic approval of every future invoice or scope change. Before using a saved card, confirm the correct client and the authority for the specific charge through the agency’s normal billing process.
The source describes saving a card and charging a saved card; it does not establish that a particular unattended billing schedule is created by that action. Plan recurring work and its payment process explicitly. State which amounts and timing the client has agreed to, who initiates or reviews the charges and how changes are handled. Avoid promising automation that has not actually been configured and verified.
Verify the client, relevant invoice or agreed work, amount and authorization under the agency’s billing arrangement. Check that the same payment has not already been completed while someone was investigating a status issue. Use the proper payment records rather than a note saying the client “probably paid.” A deliberate check is especially useful when several agency staff can respond to the same billing question.
The product describes overdue invoices appearing in Mission Control. Use that visibility to assign a review rather than assume the reason for non-payment. A billing contact may need an explanation, a correction or an internal reference before approving the invoice. Coordinate with the account owner so a reminder reflects the actual situation and does not contradict a resolution already being discussed with the client.
Confirm that the correct receiving account is connected and review the intended client invoice and portal payment route using the agency’s authorized verification process. Do not create an unnecessary live charge just to prove a button exists. Define what evidence will establish the setup is ready, including the invoice identity and expected confirmation behavior. Record the result so a later administrator knows what was actually checked.
Use the invoice identifier, client identity, expected amount, time of the attempt and observed payment state. Compare those details with the relevant provider record through authorized access. Keep full card details, private tokens and unrelated client information out of support messages. The goal is to identify one transaction accurately, not collect sensitive payment information that the team does not need for the investigation.
No. The source distinguishes invoices the agency sends to its clients from the agency’s own Agency Pilot subscription and credit-pack purchases. Both involve Stripe, but they concern different billing relationships. When asking about a charge or reviewing records, specify which relationship and invoice you mean. This prevents the team from investigating the agency’s software bill when the actual question concerns a client payment into its connected account.
The documented disconnect is an integration action, not a refund instruction. Do not assume it reverses payments, cancels every invoice or closes the external provider account. Before disconnecting, review outstanding billing work and the intended future payment route. Handle any payment correction through the appropriate established process and verify its outcome separately from removal of the connection.
The source states that Stripe’s standard fees apply. Use the agency’s own provider account and applicable pricing information to establish actual charges, rather than treating a generic integration guide as a quote. Assign someone to review the provider records as part of reconciliation. Keep client invoice amounts and provider fees distinct in internal discussions so the team can explain the transaction without confusing the amount billed with other account activity.
Record the receiving account, authorized billing owner, invoice workflow, saved-card practices and open payment questions. Make sure the incoming person understands how to verify a confirmed payment and distinguish client invoices from the agency’s own subscription charges. Transfer responsibility through appropriate account access rather than sharing secrets in a document. Review the setup when the agency business structure or client billing process changes so the connection continues to match the intended arrangement.
