Skip to content
Create account
or
Sign in
The Stripe Docs logo
/
Ask AI
Create account
Sign in
Get started
Payments
Finance automation
Platforms and marketplaces
Money management
Developer tools
Get started
Payments
Finance automation
Get started
Payments
Finance automation
Platforms and marketplaces
Money management
Overview
Versioning
Changelog
Upgrade your API version
Upgrade your SDK version
Developer tools
SDKs
API
Testing
Workbench
Event Destinations
Workflows
Stripe CLI
Stripe Shell
Developers Dashboard
Agent toolkit
Stripe health alertsBuilding with LLMsStripe for Visual Studio CodeFile uploads
Security
Security
Extend Stripe
Stripe Apps
Stripe Connectors
    Overview
    Integrate a connector
    Commercetools
    Adobe Commerce
    Mirakl
    NetSuite
    Oracle Opera
    Cegid
    PrestaShop
    Salesforce
      Stripe Connector for Salesforce Platform
        Installation
        Configure events
        Enablement
        Configuration
      Stripe Billing for Salesforce CPQ
      Salesforce B2C Commerce
    SAP
    Shopware 6
    Stripe Tax for WooCommerce
    Stripe Tax for BigCommerce
    Partner connectors
    Build your own connector
Partners
Partner ecosystem
Partner certification
HomeDeveloper toolsStripe ConnectorsSalesforceStripe Connector for Salesforce Platform

Stripe for Salesforce Platform Configuration

Copy page

Switch Stripe account authentication from OAuth to API key

As of version 1.17 of the Stripe for Salesforce Platform, we no longer offer OAuth-based authentication. To migrate your Stripe account from OAuth to use an API key, follow these steps:

  1. From the Salesforce Setup tab, go to App Launcher > Stripe for Salesforce Platform.

  2. In Account Management, click on the Stripe account you want to migrate.

  3. Click Reauthorize using API key.

  4. Input the Stripe API Key for this account, ensuring that the API key is for the right mode (live or test). Click Save.

Work with Sandboxes and environment clones

When creating a sandbox or copying production data, ensure the Stripe for Salesforce Platform omits select data from the clone. Don’t copy connections and configurations from production or other environments. Use sandbox templates that don’t include any stripeGC objects.

Configure the Stripe for Salesforce Platform independently on each Salesforce Org and run the setup process on each Salesforce Org.

Remove data copied to a clone

When you copy data from the StripeGC objects to a new Salesforce Org, remove the data by running an Anonymous Apex script to delete it:

delete [SELECT Id FROM stripeGC__Setup_Data__c]; delete [SELECT Id FROM stripeGC__Stripe_Account__c]; delete [SELECT Id FROM stripeGC__Stripe_Event__c]; delete [SELECT Id FROM stripeGC__Stripe_Webhook_Endpoint__c]; delete [SELECT Id FROM stripeGC__Sync_Log__c];

Default Events excluded from recursion detection

Stripe’s Salesforce Platform has checks to prevent actions from getting stuck in a loop. A logical loop might happen when a set of resources constantly detects and responds to updates from another set. For example, suppose you have one flow that listens to Stripe’s customer.updated events and updates a Salesforce Account. Meanwhile, you have another flow that detects updates to the Salesforce Account and updates a Stripe customer. This setup leads to a recurring loop, which would continue indefinitely.

charge.capturedcharge.expiredcharge.failed
charge.pendingcharge.refundedcharge.succeeded
charge.updatedcredit_note.createdcredit_note.updated
credit_note.voidedinvoice.createdinvoice.deleted
invoice.finalization_failedInvoice.finalizedinvoice.marked_uncollectible
invoice.paidinvoice.payment_action_requiredinvoice.payment_failed
invoice.payment_succeededinvoice.sentinvoice.upcoming
invoice.updatedinvoice.voidedinvoiceitem.created
invoiceitem.deletedinvoiceitem.updatedissuing_card.created
issuing_card.updatedissuing_cardholder.createdissuing_cardholder.updated
issuing_dispute.closedissuing_dispute.createdissuing_dispute.funds_reinstated
issuing_dispute.submittedissuing_dispute.updatedissuing_transaction.created
issuing_transaction.updatedmandate.updatedorder.created
order.payment_failedorder.payment_succeededorder.updated
payment_intent.amount_capturable_updatedpayment_intent.canceledpayment_intent.created
payment_intent.partially_fundedpayment_intent.payment_failedpayment_intent.processing
payment_intent.requires_actionpayment_intent.succeededpayment_link.created
payment_link.updatedpayment_method.attachedpayment_method.automatically_updated
payment_method.detachedpayment_method.updatedpayout.canceled
payout.createdpayout.failedpayout.paid
payout.updatedquote.acceptedquote.canceled
quote.createdquote.finalizedsetup_intent.canceled
setup_intent.createdsetup_intent.requires_actionsetup_intent.setup_failed
setup_intent.succeededcustomer.source.createdcustomer.source.deleted
customer.source.expiringcustomer.source.updatedsource.canceled
source.chargeablesource.failedsource.mandate_notification
source.refund_attributes_required

Recursion detection configuration

You can include and exclude specific events from recursion detection. If you’re an admin, you can modify these events in your settings by configuring recursion detection.

The Recursion Detection Configuration can be accessed by following these steps:

  1. Navigate to Setup > Custom Code > Custom Metadata Types.
  2. Under Recursion Detection Configuration, click Manage Records.
  3. Next to Default, click Edit.

Within this configuration, an admin can add either Included Events or Excluded Events.

Configure sync preferences

  1. To configure Sync Preferences, launch the Stripe Connector for Salesforce App wizard, navigate to App Launcher > Stripe Universal Connector for Salesforce
  2. Click the Sync Preferences button.
  3. Enable or disable Enable Stripe Event Data Cleanup.
  4. Modify the Maximum Stripe Event Records Retained (Count).
  5. Enable or disable Sync Log Records.
  6. Modify the Maximum Sync Log Records Retained (Count).

See also

  • Enablement
  • Installation guide
Was this page helpful?
YesNo
Need help? Contact Support.
Join our early access program.
Check out our changelog.
Questions? Contact Sales.
LLM? Read llms.txt.
Powered by Markdoc