Vendor pluginLast verified 2026-09-11 · Reviewed by a person 2026-09-25
Yes. PayPal publishes and supports its own free SFRA cartridge, PayPal Complete Payments for B2C Commerce (int_paypal plus bm_paypal, AppExchange version 3.44), and PayPal's developer site links SFCC merchants to it. The renamed Braintree cartridge, PayPal Enterprise Payments, is a separate PayPal listing, and Salesforce Payments can also run PayPal and Venmo natively. None of the three is documented for SiteGenesis or PWA Kit storefronts.1
UAT-Ops testing: PayPal's sandbox was verified by UAT-Ops on 2026-09-11 with the directory's card flow (5 passed) → evidence on the PayPal hub. The Salesforce Commerce Cloud (B2C) integration itself has not been run.
Sources checked: 14 claims from 4 sites, listed at the foot of the page.
Connects through LINK cartridge set int_paypal (storefront) and bm_paypal (Business Manager) added to the SFRA cartridge path, with metadata imported and the PayPal REST client ID and secret stored as service credentials; it uses the Orders API for checkout and the Payments API for capture, refund and void from Business Manager. Biggest gotcha: Three PayPal paths, two AppExchange listings.
How it connects
Method
LINK cartridge set int_paypal (storefront) and bm_paypal (Business Manager) added to the SFRA cartridge path, with metadata imported and the PayPal REST client ID and secret stored as service credentials; it uses the Orders API for checkout and the Payments API for capture, refund and void from Business Manager2
Maintained by
PayPal (AppExchange publisher; support contact at paypal.com)1
Free on AppExchange; PayPal's own transaction fees apply1
Requires
SFRA only; implementation guide 24.2.0 targets SFRA 7.0.0 and was tested with Compatibility Mode 21.21
Checkout modes
smart payment buttons, card fields, express checkout, apple pay2
What works on this platform
Yes: a source confirms it on this integration. Not verified here: the gateway supports it, but no source confirms this integration exposes it. No: not available. A capability with no source either way is left off.
PayPal Card Fields through the JavaScript SDK; requires Advanced Credit and Debit Card Payments on the PayPal account, and the card types set up in Business Manager must match PayPal's supported list.
From 24.2.0 a Vault flow replaces the deprecated Billing Agreement flow for PayPal and cards; a migration job converts stored Billing Agreement IDs to vault tokens.
Level 2 and 3 data for Apple Pay, cards, PayPal, Venmo and local methods once enabled in Preference Configuration; commodity code, unit of measure and ships-from postal code are not passed.
PayPal supports this; no source confirms it on this integration.
Capability status reflects the integration and documentation available at the time of verification, not necessarily every capability of the underlying gateway or platform.
Testing it
Start from an SFRA site on a B2C Commerce sandbox and import the cartridge metadata. Create a sandbox REST app on the PayPal Developer Dashboard, enable Advanced Credit and Debit Card Payments under Features > Accept payments, and enter the client ID as the user and the secret as the password in Business Manager > Administration > Operations > Services > Credentials (Paypal_Sandbox_Credentials). Use the Test connection with PayPal button under Merchant Tools > PayPal plugin > Preference configuration. For webhooks, add a webhook on the same REST app pointing at your sandbox host's Paypal-WebHooks controller URL, subscribe only to the eight supported events, and paste its ID into the PP_WH_ID site preference. Pay with a PayPal sandbox buyer and with PayPal test cards, then assert the order status in the Transactions module, that a refund made in the PayPal dashboard reaches the order through the webhook, and that a 3DS challenge card behaves as configured.2
UAT-Ops runs integration flows like this against the real sandbox and keeps the evidence. Get one email when it opens.
Gotchas
Three PayPal paths, two AppExchange listings
PayPal publishes two separate SFRA cartridges on AppExchange: Complete Payments (int_paypal) and Enterprise Payments (formerly Braintree, int_braintree). Salesforce Payments can also connect a PayPal account natively. PayPal's developer plugins page points SFCC merchants to Complete Payments. Its "Braintree for Salesforce Commerce Cloud" link, however, opens Braintree Payments for Order Management, a different product. Decide whether you hold a PayPal REST app or a Braintree merchant account before choosing a cartridge, because the two use different credentials, cartridges and webhook consoles.
AppExchange shows the Complete Payments listing at version 3.44. PayPal's implementation guide numbers the cartridge 24.2.0 instead, so the two figures cannot be compared directly. The guide targets SFRA 7.0.0, but its list of overridden templates says those templates match SFRA 6.3.0. Because int_paypal overrides checkout, cart and login templates, diff them against your own SFRA version. The Braintree cartridge guide supports SFRA 6.3.0 only.
The cartridge does not register its own webhook. You create one on the PayPal REST app pointing at the site's Paypal-WebHooks controller, then paste the webhook ID into the PP_WH_ID site preference. Only eight authorization, capture, vault and dispute events are supported. If PP_WH_ID is missing or wrong, refunds made in the PayPal dashboard will not reach the order.
Billing Agreements and the OCAPI cartridge are retired
From 24.2.0, stored PayPal accounts move from Billing Agreements to vault tokens. PayPal recommends running the migration job before upgrading; otherwise conversion happens on the fly at login. The headless int_paypal_ocapi cartridge stopped at 24.1.0 and is no longer maintained, and neither AppExchange listing covers PWA Kit.
Communication log writes PII and secrets in cleartext
The guide recommends turning on the int_paypal.http.rest communication log while debugging. It also warns that the log records customer addresses, phone numbers, emails and some credentials in cleartext, so switch it off straight after use, and never leave it on in production.
Last verified 2026-09-11 · Reviewed by a person 2026-09-25
Integration capabilities, requirements, pricing, availability, and vendor policies may change over time. UAT-Ops documents information based on the authoritative sources and testing available at the time of review.
Where newer information, testing, or vendor documentation materially changes a published claim, UAT-Ops may revise the page to reflect the most current verified information. Readers should confirm time-sensitive requirements with the relevant vendor before making production or purchasing decisions.