Set Up Stripe Payments with Salesforce in Titan

Business Background

When you need to accept online payments and connect payment activity to Salesforce, you can use Stripe payments with Salesforce through Titan. This helps you collect payments from users while keeping payment details connected to the records and processes your team already manages.

Stripe can be used for payment flows such as product purchases, service payments, subscriptions, registration fees, donations, or marketplace transactions. Once the payment is completed, your project can automatically proceed to the next step, such as confirming the payment, redirecting the user, or updating Salesforce.

Titan Solution

Titan lets you add Stripe as a payment option in your project and connect the payment process to Salesforce. You can configure payment settings to suit your business needs, including support for multiple currencies and recurring payments.

You can also define what happens after payment. For example, you can send an email, redirect the user to another internal or external page, or push payment data to Salesforce. This helps you manage the payment journey and keep your Salesforce records up to date without manually handling each step.

How to Guide

Note:

Prerequisite:

Configure Payment

1. Select the Stripe option. The Payment Configuration > Payment Method screen opens.

2. Set up the following:
   1. Payment Method
   2. Processor Configuration
   3. Layout
   4. Post Payment
   5. Salesforce Integration

Payment Method

1. Use the drop-down list to select a currency. This is a list of the currencies that Stripe supports. The options are:
   • Dollars
   • Euros
   • CHF Francs
   • Australian Dollar
   • Canadian Dollar
   • Israeli New Shekel
   • Pound Sterling
   • New Zealand Dollar
   • Dynamic

Note:

You can select “Dynamic” to give the end-user the option to add a currency type not listed.

Add the dynamic value as a variable. The string must be as follows, for instance:

• ILS
• USD
• EUR
• GBP

Stripe will reject any other values. Please refer to the API for more information on different currencies.

2. Use a radio button to select one of the following:
   • Single Payment: Only a single payment will be deducted.
   • Recurring payment: A recurring payment is an automatic payment charged to a customer’s credit/debit card each time the payment is due until the customer notifies the vendor. Merchants must first get permission from the consumer; for instance, for membership fees.
   • Token: A token number is stored in Salesforce for later use. This token can be used later to charge the credit card without having the actual card details. A payment is not created when the token is generated.

3. If using Recurring payments, click the Gear icon. The Configure Recurring Settings screen opens.
4. Select the payment period using a radio button:
   • Daily: the recurring payment will be made every day.
   • Weekly
   • Monthly: this is the default option.
   • Yearly
5. Select the number of charges using a radio button. This is the number of recurring payments that the user will make.
   • Unlimited
   • Limited
     • Add the total charges in the field.
6. Use the drop-down list to select the following:
   • Static: Add a number in the field.
   • Field: Use the drop-down list to select a field.

Note:

The Published Webhook URL is necessary for triggering recurring payments in Titan after the initial payment through Stripe.

A webhook is an HTTP endpoint that receives events from Stripe. Refer to the Stripe documentation to use the webhook to trigger recurring payments.

7. Click the Apply button.
8. Click the Next button. The Payment Configuration > Processor Configuration screen opens.

Processor Configuration

Configure the following as necessary:

• Required processor configuration
• Structured Parameters
• Custom parameters
• ACH

Required

1. For the Required processor configuration, do the following:
   • Type the Secret Key and the Public Key in the fields.
     • These are mandatory fields and both are validated for valid keys.
     • Make sure that you do not paste the secret key in the public field.
   • Use the Dynamic description toggle switch as follows to describe what the payment is for:
     • Leave the toggle switch in the default position (off) and add a description in the field.
     • Alternatively, switch the Dynamic description on and use the drop-down list to select a description.
   • Set strong customer authentication by using the Use SCA toggle switch.
   • Use the toggle switch to enable idempotent requests.
     • Idempotency is used to safely retry requests to avoid performing the same operation twice.
     • You can create or update an object using an idempotency key so that, in case of a connection error, you can safely repeat the request without the risk of creating a duplicate object or performing the update twice.
   • Use the drop-down list to select the map customer option. You should have added the option as a variable.

Structured Parameters

1. Click the Structured Parameters option.
2. Use the toggle switch to enable the structured parameters.
3. Use the Field or Static options to add parameters.
   • Use the drop-down list to select a Field parameter.
   • Type a Static parameter in the field.

Custom Parameters

1. Click the Custom Parameters option.
2. Use the toggle switch to enable the custom parameters.
3. Complete the fields.
4. Use the Field or Static options to add parameters.
   • Use the drop-down list to select a Field parameter.
   • Type a Static parameter in the field.
5. Use the Add a Parameter option to add more parameters.

ACH

1. Click the ACH option.
   • ACH lets you accept payments from customers with a US bank account.
2. Use the toggle switch to enable ACH.
3. Use the toggle switch to enable Allow ACH Bank Transfer.

4. Use the toggle switch to enable Allow Plaid. (Plaid and Stripe have joined forces to provide effortless money transfers, eliminating the need to manually deal with account or routing numbers.)
   • Type the Plaid Secret Key and the Plaid Client ID in the fields. These are mandatory fields.
   • Use the drop-down list to select the Plaid environment. The options are:
     • Production
     • Development
     • Sandbox

5. Click the Next button. The Payment Configuration > Layout screen opens.

Layout

1. Add a label in the field.
   • This is mandatory.
   • This description will appear on the Configure Project Payments Settings screen under the My Payments list.
2. Add a preloader message in the field.
   • This is mandatory.
3. Use the drop-down list to select the amount.
   • This is mandatory.
   • You must have added the amount as an input element or variable on your project.

4. Click the Next button. The Payment Configuration > Post Payment screen opens.

Post Payment

Note:

Post-payment actions are not mandatory.

You can do the following:

• Send an email.
• Redirect the user to an internal and/or external link when the payment processing has finished.
• Redirect the user to an internal and/or external link when the payment processing has failed.

1. To send an email, use the toggle switch to switch on the option.
   • You can configure an email that will be sent when the transaction has been processed.
   • Select the configured email.

2. Select the Redirect on Success option, if necessary
3. Use the toggle switch to switch on a redirect action on success action.

• Configure an External redirection.

• Configure an Internal redirection.

4. Select the Redirect on Failure option, if necessary
5. Use the toggle switch to switch on a redirect action on failure action.

• Configure an External redirection
• Configure an Internal redirection

6. Click the Next button. The Payment Configuration > SF Integration opens.