Stripe Specific
The Statement Description on Card holders account comes from the Merchant Facility-> "Organisation Name" field.
This generally means the Webhook Secret Key has not been setup correctly.
- Please re-apply the procedure Stripe Webhook Secret Key setup. In particular, make sure you copy the secret key after revealing and not the webhook reference.
- Also, you may need to re-authorise Payments2Us App
Locate the Payment Txn that you are looking to have investigated, then locate:
- Payment Confirmation No.
- If the Payment Confirmation No. is blank, then use Payer Id
Login to Stripe Dashboard, then go to:
- For production: https://dashboard.stripe.com/logs
- For Test/Sandbox: https://dashboard.stripe.com/test/logs
Paste the valued (Payment Confirmation No. OR Payer Id) from above into the search box and press enter (1)
Then copy the value of the id beginning with "req_". This is what you need to send to Stripe support.
For some themes, the Expiry date and CVV can be a little light and harder to see. User will see this when entering the card details.
Should this be a concern, you can:
- Select a different "Theme" option on the Merchant Facility
- Change the Payment Gateway on the Merchant Facility to "Stripe SCA". This is the preferred option for Stripe as it uses their newer APIs
- Get your web developer to setup custom theme. Note, custom themes do have an extra monthly cost and should your web developer have questions that cannot be answered from the help guide, then you may need a Premium Support Block to assist. The advantage to this option though is your form would better match the rest of your websites branding.

For Stripe, the section highlighted below is controlled 100% by Stripe. It is hosted on their server.
There is no way to split this out or separate these fields. The Payments2Us Payment Form builder has no influence on these fields.

If you are getting an email from Stripe Saying you are getting a Webhook Failure, then check:
- Go through the Stripe setup process again. Make SURE you have used the Reveal for the secret key, vs. copying another reference shown on the page.
- Recheck all Sharing Rules have all been setup correctly. Suggested Sharing Rule setups do change from time to time.
- The Payment Txn is located by the "TxnRef" field AND Last Modified Date (Created date prior to version 9) is in the last 5 days. Probably it can occur when your admin has enabled Create Audit Fields - please get this turned off.
For Stripe SCA, the Credit Card details do not show until the "Next" button is pressed. This is due to the way Stripe SCA works and its method of managing security features such as Secure 3D.

See payment gateway comparison for an up-to-date comparison between gateway options.
The "SCA" in "Stripe SCA" stands for Strong Customer Authentication. This means it includes Secure 3D anti fraud functionality to make transactions more secure.
Any new functionality of Payments2Us will only be added to "Stripe SCA". Currently a big difference is Apple Pay and Google Pay are only available with "Stripe SCA".
One key user experience difference is "Stripe SCA" requires users to press the "Next" button before the credit card/payment details section will show.
For Stripe, all external facing forms require a CCV
When you are logged in as a Salesforce user, CCV is optional with:
- Batch Entry
- Transact Payment (Note, this can work with once-off or recurring setup)
- Import Files (Note, this can work with once-off or recurring setup). Also see the Import Files FAQ.
Stripe does NOT provide use with the ability to just update the expiry date. That is why the message on the Card Expiry Update shows.
Some gateways do provide this. You can see a comparison at: https://help.payments2us.com/m/installation/l/1284641-what-are-the-differences-between-payment-gateways
You'll need to do a full Card Update with Stripe but using the "Card Update" button/component on the Recurring Payment Object. Alternatively send the Card Update link to the Card Holder so they can update the details.
Follow up question we some times receive: Can we update the expiry date within the Stripe Dashboard.
Unfortunately this update within Stripe will not sync back to Salesforce. For the next charge, we will still be sending the old expiry date and this will cause the payment to fail.
You'll need to use the Card Update and enter the full details from the Recurring Payment, or send the Card Update link to the Card Holder so they can update the Card Details.

Stripe needs Expiry date in correct format and therefore the Card Expiry Date is editable by anyone. We have a different field "Expiry MMYYY" which can be edited and that in turn will update the "Card Expiry Date".
"Expiry MMYYY" field might not be available by default and you may need to add it from page layouts.
When you are processing a Batch Entries or Import Files you might get error message as below
This is because stripe has recently made some changes to their API wherein you have to enable the below setting when you send credit card numbers to their API.
Login to your Stripe account and go to Business settings | Integration | Advanced Settings. Enable Process payments unsafely.
Please note that the above changes are only required for Batch Entries or Import Files, normal checkout form uses the updated API and will not require any changes.
Stripe allowed users that registered before 2017 to continue using the API without throwing this security issue. Only newly registered users get this warning so they may be able conceive the payment differently using the new token mechanism released in April 2019