Salesforce payment processing: choose a route 2026
Identify the Salesforce payment product and provider your store needs, then check the connection between the transaction, receipt and customer order.
- Published
- Last updated
Salesforce payment processing works through a payment service or provider app matched to your Salesforce product. Use Salesforce Payments for its supported commerce checkout or Pay Now workflows. Use the official Stripe app when you need to build payment actions and record updates inside Salesforce.
The deciding question is where the sale lives. A storefront order, a billing invoice and a sales opportunity need different connections. A successful provider transaction must reach that original record before staff issue a paid receipt or release an order.
Identify the Salesforce product first
Choose the payment route from your existing Salesforce product and the record you need to update. The name Salesforce alone doesn’t identify a checkout or a payment gateway integration.
| Your workflow | Documented route | Connection type | Prerequisite that changes the choice |
|---|---|---|---|
| B2B or D2C Commerce checkout | Salesforce Payments | Native Salesforce payment service with supported providers | Payments entitlement and store configuration |
| Payment link from a Salesforce record | Salesforce Pay Now, powered by Payments | Native payment-link workflow | Payments setup and a Pay Now store |
| B2C Commerce storefront | Salesforce Payments for B2C Commerce | Native checkout with provider-specific configuration | B2C Commerce setup, separate from core-platform store settings |
| Payment actions inside a CRM workflow | Stripe app for Salesforce Platform | Official Stripe app plus configured Flow or Apex logic | Stripe account, installed packages and explicit record mapping |
| Revenue Cloud Billing invoices | Salesforce Payments under the Billing setup | Product-specific native gateway route | Revenue Cloud Billing licence and its payment configuration |
Salesforce documents Pay Now links that can attach to any Salesforce object. Attaching a link to a record does not establish your business rule for marking an invoice paid. Keep that rule explicit in the integration. Read the Salesforce Payments overview for the commerce and payment-link routes.
Salesforce’s B2C documentation names Adyen, Stripe and PayPal. Its Revenue Cloud Billing instructions describe a Stripe-powered Salesforce Payments route. Those product instructions are separate. Don’t copy B2C provider settings into a Billing implementation.
Australia is a supported Stripe account country. Salesforce’s Payments overview excludes merchants contracting with Salesforce and based in Brazil, India or Japan. Australian eligibility still depends on the chosen gateway and payment method. Merchant location, customer location and transaction currency are separate inputs. Salesforce’s B2B payment-method tables give method-specific restrictions.
The Stripe app for Salesforce Platform is an integration builder. It exposes Stripe actions through Salesforce Flow Builder and Apex. Custom record updates remain implementation work even though the app is official. Agentforce itself is not the payment provider in these routes.
Budget for the Salesforce entitlement, provider transaction fees and implementation work. Event monitoring and reconciliation also need ongoing ownership. A connector licence alone doesn’t describe the whole operating cost.
Map the transaction to the retail record
Map every payment attempt to its original order or invoice and keep the provider’s transaction reference with it. A customer match alone is too broad when the same person has several unpaid orders.
For a Stripe workflow, retain the Stripe account and environment alongside the PaymentIntent reference. Store the Salesforce record ID in the mapping your integration uses. Keep the event ID when an incoming event updates the record. These references let staff investigate an attempt without taking another payment.
The payment states answer different questions.
| State | What it establishes | Evidence to inspect |
|---|---|---|
| Authorisation | Funds are reserved for a later capture | Provider authorisation result and capture deadline |
| Capture | The reserved payment is collected | Provider capture result and charge reference |
| Refund | A reversal has its own processing state | Refund reference, amount and provider status |
| Settlement and payout | Funds become available and then move towards the bank | Provider balance activity, payout reference and bank receipt |
Stripe’s manual capture guidance distinguishes the hold from capture. Stripe’s payout guidance separates balance availability from bank payouts. An authorised order is not evidence of a bank deposit.
For native Commerce with Order Management in the same Salesforce organisation, Salesforce assigns checkout authorisation to Payments. Order Management handles capture and post-order payment tasks. For the Stripe app route, your configured workflow must map the provider result to the retail record.
Consider a fictional order, R-1042, for $180. Your payment workflow stores its Stripe payment reference against R-1042. An authorisation leaves the order awaiting capture. After a confirmed successful capture, the workflow records the collected amount and creates one payment confirmation.
A later $40 refund gets its own reference and status. The remaining collected amount is $140 before fees and any other adjustments.
Incorrect: staff mark R-1042 settled because the checkout page closed. Correct: staff inspect the linked provider attempt, then use its confirmed result for the order status. Bank reconciliation remains a separate job.
Connect and verify the supported route
For a CRM payment workflow, install the official Stripe app in a Salesforce test environment, then build and verify the record mapping. The sequence below uses that route throughout. It does not use Salesforce Payments’ Commerce Setup Assistant.
- Enable Lightning Web Security in Salesforce Session Settings. Install the Stripe app using its test-environment option. Stripe recommends Install for Admins Only so access can be assigned deliberately.
- Open Stripe for Salesforce Platform from App Launcher. Start its setup wizard and authorise access to the Salesforce organisation. Add the Stripe test account with its publishable and restricted access keys. Complete the required API extension installation. Follow Stripe’s installation instructions for the package and credential requirements.
- Give the integration user the access needed for the selected Stripe actions and destination records. Give investigating staff access to the resulting payment records. Keep credentials out of order notes and customer messages.
- Build the payment action in Flow Builder or Apex. Carry the order or invoice reference through the request and save the provider reference on the destination record. Define which confirmed result permits a receipt and which state permits fulfilment.
- Configure incoming events for that account. In All Webhook Events, select the Stripe object and required events, then save. Stripe’s event configuration guide explains how these events become Salesforce records for record-triggered flows. Map each result to the original attempt and ignore already-processed event IDs.
- Assign exceptions to a named role before testing. For example, the payments operations lead owns an unmatched provider result. The Salesforce administrator owns a failed record-update flow. Record who takes over when either person is unavailable.
Stripe’s configuration guide distinguishes event-driven custom flows from Stripe Billing data sync. Billing sync supports real-time or scheduled updates. Turning it on doesn’t automatically create your retail order-payment mapping. Scheduled data also needs an age indicator wherever staff use it to answer customers.
Run the following checks with Stripe’s test payment values, using test credentials and fictional orders. Inspect saved records after each check.
| Test | Expected outcome | Exception owner if it differs |
|---|---|---|
| Successful payment | One confirmed provider payment updates the matching Salesforce record with the correct amount and reference | Payments operations lead |
| Declined attempt | The attempt retains its failure result and the order remains unpaid | Salesforce administrator for incorrect status updates |
| Browser closes before the result appears | Staff recover the original attempt by reference and reconcile its final provider state | Payments operations lead |
| Same provider event arrives again | The existing payment remains one payment and the customer receives no duplicate confirmation | Salesforce administrator |
Keep a test receipt tied to the successful attempt. Confirm the declined attempt cannot produce the same receipt. Only move the approved configuration into live service after the record and exception checks pass.
Keep customer answers and retries accurate
Give customers the confirmed payment state and send uncertain attempts to the person who can inspect them. A missing browser confirmation is an investigation trigger, not permission to charge again.
For an interrupted attempt, staff can say, “Your payment result is still being checked. Please wait while our payments team checks the original attempt.” Include the order reference in the handover. Keep provider credentials and payment-card details out of the conversation.
Before retrying, inspect the original provider payment and any later events. Stripe recommends reusing the PaymentIntent when resuming an interrupted checkout for the same purchase. Its Payment Intents guidance also describes idempotency keys for avoiding duplicate creation. Apply a stable request identity to the same operation, and keep a separate reference for a genuinely new purchase.
For a refund, “requested” and “completed” need separate customer messages. Stripe documents refunds that remain pending or fail. Read the actual refund object before saying the money has been returned. The refund guidance explains those states and the provider references staff can investigate.
A connected assistant needs the same rules as staff. Give it the order’s recorded payment state and an escalation path for stale or conflicting results. Keep capture confirmation separate from payout confirmation. When the provider and Salesforce disagree, assign the mismatch to payments operations and correct the record before sending another receipt.
Give your store its own shopping agent
Customers ask in their own words. Your agent finds, compares and checks out from your catalogue, right on your site.