Technical Website Integration Architecture
- David Fisher (Unlicensed)
- Jan Tenenberg
The feature covers the scenario when a client has an exiting website that connected to Stripe and needs to submit data to Salesforce.
npsp+ doesn’t require a direct connection between website and Salesforce, the integration works via Stripe Webhooks and metadata attached to Payment Intent/Subscription.
Supported Scenarios
https://verticconsulting.atlassian.net/wiki/spaces/VE/pages/1195835397
https://verticconsulting.atlassian.net/wiki/spaces/VE/pages/1195868168
Postman Documentation
This documentation shows the examples of passing the metadata to Stripe:
https://documenter.getpostman.com/view/5605337/TW76DjPe
You can add and run in your Postman app, make sure you setup all the variables.
Note:
There are some limits for Stripe Metadata provide below, but we’re able to use multiple keys, i.e. separate key for Contact, Account or/and Donation details.
You can specify up to 50 keys, with key names up to 40 characters long and values up to 500 characters long.
Stripe webhooks are handled by Salesforce Flows. There are default Flow templates in the package that can be cloned to implement custom client logic.
The Flow Setting metadata manages the mapping for:
Stripe webhook event
Flow API Name
The mapping between Webhook payload and Flow input parameters
Basically, it allows handling any Stripe Event Type with Salesforce Flow.
Example of the Flow Setting that covers Payment Intent Successed handling.
TBC: Input mapping considerations