Overview
This feature enables 3rd party or custom Apps that charge through Stipe to be able to create Payment Txns using Stripe's charge.succeeded or charge.captured webhook events.
This allows automated transaction creation directly from Stripe, streamlining reconciliation and reducing manual data entry.
How It Works
When Stripe triggers the charge.succeeded or charge.captured webhook event, our webhook handler inspects the metadata section of the payload. If a specific key is found, a new payment transaction will be created automatically in Salesforce.
Key: Payments2US_Webhook
Purpose: This key acts as the trigger. Its value is used to populate the AAkPay__Transaction_Source__c field on the Payment Txn record.
Other Field Mappings
Additional payment txn fields can be set by including their values in the metadata. Mapping can be done using Gateway Metadata field of Stripe Merchant facility record.
Format for Mapping in Merchant Facility:
Stripe Label[Payment Txn Field API Name]Example Mapping in Multi-Picklist:
Frequency[AAkPay__Regular_Pymt_Freq__c]
Play Date[AAkPay__Transaction_Date__c]
Example Stripe Metadata Payload
{
....
"metadata": {
"Payments2US_Webhook": "New Transaction",
"Frequency": "Monthly",
"Play Date": "21/03/2025"
}
...
}In this example:
- AAkPay__Transaction_Source__c will be set to New Transaction.
- AAkPay__Regular_Pymt_Freq__c will be set to Monthly.
-
AAkPay__Transaction_Date__c will be set to 21/03/2025.
Important Notes
- This functionality works only if the Payments2US_Webhook key is present in the metadata.
- Ensure the field mappings in the Merchant Facility are correctly formatted.
- Mapped fields must exist on the Payment Transaction object and be writeable.
- Dates and picklist values must match expected formats in Salesforce.
For setting up the Stripe webhook please refer to the Stripe Webhook Section of the help article