Stripe
This article explains how to add Stripe to your CheckoutChamp instance
Last updated
This article explains how to add Stripe to your CheckoutChamp instance
Last updated
Stripe will likely require the CheckoutChamp PCI Attestation of Compliance (AOC) for your account to process credit cards. If you have not supplied Stripe with this document then contact your CheckoutChamp Account Manager before proceeding. Additional instructions are below.
Go to Gateways > Gateway List from the navigation bar on the left and click the smaller green plus button on the Gateway List page to create a new gateway account.
Select StripeV2 from the dropdown list of gateways.
The Stripe V2 gateway includes the use of Stripe SCA (Stripe’s native 3DS solution). Stripe V2 will not impact the performance of Stripe Radar (fraud solution) as it does not require you to enable the “Handle card information directly” setting described for Stripe V1. However you can optionally enable Radar as described below.
1. Enter Merchant Information
Title
This is for internal purposes only; it helps you identify the gateway account amongst others in your instance.
secret_key
This is where you'll put your live Secret Key. This is required.
public_key
This is where you’ll put your live Public Key. This is required only if using Radar fraud prevention.
descriptorSuffix
Optionally enter a suffix which will be appended to the end of the payment descriptor on the customer’s bank statement.
To use this with multiple suffixes:
Enter one of your descriptor suffixes into the descriptorSuffix field and update the profile.
Go back to your Gateway List and use the darker blue button to duplicate the existing Stripe V2 gateway.
Modify only the descriptorSuffix and create the gateway. Repeat for all descriptors.
Navigate to CRM → Campaigns, edit the campaign and assign each gateway to the appropriate campaign product.
sendProductName
Enable this if you are required to send your product names.
sendProductAsSuffix
Enable this to append the product name on the order to the end of your payment descriptor.
sendUpsellToken
Enable this to use the payment token returned on the offer when processing an upsell. Consumers will not be offered a 3DS challenge and can complete the upsell with one click.
sendRadarSessions
disablePhone
Enable this to not send phone number to Stripe
disableEmail
Enable this to not send email address to Stripe
disableEmailReceipt
Enable this if you plan to send all of your order confirmation emails from the CRM.
doNotSendAddress
Enable this to not send the customer’s address to Stripe
doNotSendDescriptor
Enable this to not send the descriptor to Stripe
connectedAccount
Enable this if your Stripe accounts are connected. Enter the account number in the Mid # field, starting with acct_.
Connected accounts require a single webhook at Stripe for all accounts (see signingSecret notes above)
Enable zeroAuth to authenticate a card for zero amount. This could be a good alternative to a validate card trial. Do verify with Stripe that your account supports this.
Enter Customer Service Info
These will dynamically fill into the appropriate autoresponder tokens.
Enter Limits
Add Monthly Cap so you don't exceed that amount
Discount Rate - Processing fee
Transaction Fee - Per transaction fee
Reserve Rate - Used for Reserve Report
Chargeback Fee - Used for Chargeback Details Report
Enter Descriptor and Mid #
Enter the Descriptor provided by Stripe to display on autoresponders
Stripe does not provide a Mid# so feel free to store any value here. However it is required to enter a valid account number starting with acct_ if using connected accounts.
Having a phone campaign dedicated to testing new gateways and fulfillment houses is best so you do not affect live campaigns before knowing if the Gateway/Fulfillment House is working. This will also allow you to set up an offer as an un-shippable and for $1 so you aren’t charging yourself full price and shipping a product when you are only testing the gateway.
If this gateway will be used for rebills, be sure to set up a recurring offer with Cycle 2 having at least a $0.50 cent difference to avoid any duplicate transaction declines. After placing the live test order, open that customer profile click into that purchase to “Force Bill NOW” which will simulate a rebill.
While you are not testing, you can delete the campaign to remove it from reports. You can always restore a deleted campaign and it will retain the most recent settings.
If you process a live transaction and receive a decline with this message: "Sending credit card numbers directly to Stripe API is generally unsafe", you will need to enable the Handle card information directly setting inside Stripe's backend. The instructions here may be helpful but you may also need to contact Stripe support directly.
1. Enter Merchant Information
Title
This is for internal purposes only; it helps you identify the merchant account amongst others in your instance.
Username
This is where you'll put your live Secret Key
Password
Not needed any longer.
disableEmailReceipt
Enable this if you do not want Stripe to send order confirmation emails.
createCustomer
Enable this if you’d like CheckoutChamp to create a customer record in Stripe.
sendProductName
Enable this if you are required to send your product names.
Enter Limits
Add Monthly Cap so you don't exceed that amount
Discount Rate is the processing fee
Reserve Rate - Used for Reserve Report
Transaction Fee per transaction
Enter Descriptor and Mid #
2. Select Create Gateway to Save.
3. Enable the Handle card information directly setting inside Stripe's backend.
This will need to be enabled because our tokenizations do not align. Rest assured as CheckoutChamp is PCI Level 1 Certified so your credit card data is secure.
If you process a live transaction without enabling this option you will receive a decline with this message: "Sending credit card numbers directly to Stripe API is generally unsafe"
This option can be found inside Stripe's settings. Search for “integration” in the search bar and choose Settings > Integration
expand the advanced options and select "Handle card information directly".
Check all checkboxes and then choose "I collect payment information securely through a PCI compliant third party vendor" from the dropdown list. Enter “CheckoutChamp CRM” in the input field and then click the "Continue" button.
When you are done your settings will look similar to the above image and you will be ready to begin processing successfully through CheckoutChamp!
Having a phone campaign dedicated to testing new gateways and fulfillment houses is best so you do not affect live campaigns before knowing if the Gateway/Fulfillment House is good to go. This will also allow you to set up an offer as an un-shippable and for $1 so you aren’t charging yourself full price and shipping a product when you are only testing the gateway.
If this gateway will be used for rebills, be sure to set up a recurring offer with Cycle 2 having at least a $0.50 cent difference to avoid any duplicate transaction declines. After placing the live test order, open that customer profile click into that purchase to “Force Bill NOW” which will simulate a rebill.
While you are not testing, you can delete the campaign to remove it from reports. You can always restore a deleted campaign and it will retain the most recent settings.
Stripe V2 can optionally use Radar fraud prevention. Enable the “Handle card information directly” setting on your Stripe account as described for Stripe V1. Enter public_key and check the sendRadarSessions box. As with 3DS, this requires the checkout page be coded to handle Merchant Redirect exceptions described .
More information is
2. Before going live with this gateway, be sure to perform a .
Alternatively, use this direct link:
For Stripe SCA (Strong Customer Authentication) your checkout page must support . There is more on SCA .
4. Before going live with this gateway, be sure to perform a .
