If you have any queries regarding other payment gateways, please email support@payments2us.com
How can I handle credit card and paypal on the same Payment Form. Do I need to have two webhooks on the same Payment Form?
Your question might also look like " I have Stripe and Paypal both option on Paym ...
Your question might also look like " I have Stripe and Paypal both option on Payment Form and I do need both to be configured both on single form but payment form only gives me the option of single webhook key. It seems that you either need to go with Stripe or with Paypal, but the solutions is to use a different payment form for each. Attached a picture of the form's section."
Whilst the webhooks are specified at the Payment Form level, they are NOT specific to that Payment Form. You can create two Payment Forms, one for Stripe, one for PayPal and enter the corresponding webhook in each respective Payment Form. So you would specify Stripe and the Stripe Webhook Secret Key on Payment Form 1.
And specify PayPal and the PayPal Webhook Secret Key on Payment Form 2.
You can then use Stripe or PayPal as checkout options with with Payment Form.
How do we setup a test Merchant Facility?
The simplest way is to use the Create Samples from the About Payments2Us Tab. Thi ...
If you have created a Full or Partial Sandbox and that has included copies of your Merchant Facility, then you will first need go to the Merchant Facility Tab, then rename the DEMO FACILITY or delete it. Then use the Create Samples again from the Merchant Facility.
If you want to test using your payment gateway specific, vs. the Windcave generated one, or you wish to see the transactions in the Payment Gateways online portal, then you will need to contact the Payment Gateway directly and setup your own test account. Most Payment Gateway providers provide an online option for this, some require you to lodge a support request.
TIP: If creating / generating a new new test/demo facility, you will most likely need to re-authorise Payments2Us.
A credit card is being declined and it should not happen
Payments2Us integrates with a Payment Gateway. The Payment Gateway is what valida ...
Payments2Us integrates with a Payment Gateway. The Payment Gateway is what validates and charges a card. The success/response is recorded back in Salesforce (1).
For some gateways, such as Windcave, you need to get card types as Amex or Diners setup as a separate Merchant Facility. Contact support@payments2us.com if using Windcave payment gateway only.
For all other Payment Gateways, you'll need to contact the payment gateway provider directly. Provide them the date/time, amount, card holder name and transaction references (2). They will be able to provide you with a reason of why the card was declined.
Blackbaud - Application not connected to Blackbaud Environment Error
During the Blackbaud authorisation process, if the Blackbaud screen shows “This a ...
During the Blackbaud authorisation process, if the Blackbaud screen shows “This application has not been connected to your Blackbaud environment” error.
Then in order to resolve this error you need to connect your application to the Blackbaud environment. You can follow the steps listed in the Blackbaud video guide in order to connect your application to the environment:
Video:
Blackbaud - Payment Configuration CSC Level
Following Blackbaud document list down the behaviours of different CSC level of a ...
Following Blackbaud document list down the behaviours of different CSC level of a Payment configuration:
If the payment configuration used for payments has CSC level set to Light or Full then you might face following error message on recurring payments and token charge payments:
A validation error occurred. Validation error code: <CardSecurityCodeIsRequired> Validation error message <A card security code is required.>
In order to avoid this error, either set the payment CSC level to None in Blackbaud or you can add names of 2 payment configurations separated by comma in the PxPay/PxFusion UserId. So that payment configuration (name after comma) with CSC level set to None will be used for recurring donations. Make sure that following is the order:
Payment configuration name (for credit card donation)
In payment methods find Apply pay and do the following steps
Expand the Apple Pay section by clicking on ‘>’
Press Configure Button
NOTE: If testing, enable Test Mode before Configuring.
This will redirect you to the payment method domains tab. Here complete the following steps:
Press Add new domain button (1)
Add the domain name of the website where your payment form will be framed (e.g your website )
Download the Verification File (2)
Upload the file on your website and make sure it is accessible to read (this will be on your cpanel of website hosting).
Click on Verify to confirm the upload.
Network Tokenization and Charging Expired Cards
This article only applies to EziDebit and Stripe Payment Gateways ! What is N ...
This article only applies to EziDebit and Stripe Payment Gateways !
What is Network Tokenization:
Some payment gateways support network tokenization, which lets you to keep charging a card even after the card has expired and this happens because the expiry date is automatically updated by the payment gateway on their systems against that token. This means that you do not need to ask your donors to update their card details for reasons related to card expiry.
Commonly Asked Questions and Answers
Below covers some common questions we get asked -
Q1. Why is the credit card expiry date missing on the Recurring Payment / Payment TXN inside Payments2us?
Ans. Although the card expiry date is captured at the time of the transaction, payment gateways that support network tokenization do not send this to Payments2us and simply return the billing token. The billing token is then automatically updated at the payment gateway with the correct expiry periodically, whenever they fetch this information from the card issuer. Hence, the card expiry date fields will show blank in the Recurring Payment / Payment TXN fields of Payments2us.
Q2. “Do I need to send card update emails to donors using these payment gateways that support network tokenization” or “Why am I sending card update emails to donors if our gateway uses network tokenization”?
Ans. If your payment gateway supports network tokenization, the card details are automatically updated on their end without needing manual updates inside Payments2us (as explained in Q1 above). The expiry date fields inside Recurring Payment / Payment TXN are then blank. Hence, in this case, the automation that sends these automated card-expiry emails 7 days before card expiry will simply not get triggered for these cards i.e. your donors will not receive any card update emails. The card will continue to be charged successfully.
Note: If your payment gateway supports network tokenization, but your payments are failing for reasons suspected to be related to card expiry, please contact the payment gateway directly for support and not Payments2us, because we do not have visibility into how they handle cards, tokens, and their expiry internally.
Payment Gateways and Relevant articles with further details on this functionality:
Overview This article explains how to check whether your payment gateway is opera ...
Overview
This article explains how to check whether your payment gateway is operating normally and provides direct links to the official status or incident pages for supported gateways.
If you notice issues such as delayed transactions or missing updates, checking your gateway’s status is the first step before raising a support ticket.
When Should I Check the Payment Gateway Status?
You should review your payment gateway’s status whenever you experience any of the following:
Transactions are not being processed as expected.
You see timeout or proxy errors, such as: “Payment Failed – Gateway error. IO Exception: Unable to tunnel through proxy. Proxy returns 'HTTP/1.1 503 Service Unavailable.'”
Webhooks or receipt updates are missing or delayed.
There’s a suspected outage or slow performance not related to Salesforce configuration.
Confirming the gateway’s operational status first can help identify if the issue is external before contacting support.
How to Check the Status
Most payment gateways provide a public Status Page or Incident Dashboard showing current and past incidents, planned maintenance, and uptime history. You can use these pages to verify if there’s a known outage or maintenance window affecting your transactions.
Direct Links to Gateway Status Pages
Below are the direct links to check the real-time status for commonly used gateways:
For any other inquiries, please contact support(at)payments2us.com.
Understanding 3D Secure (3DS) and How It Works with Payments2Us
Overview 3D Secure (also known as 3DS or Secure 3D) is an additional layer of aut ...
Overview
3D Secure (also known as 3DS or Secure 3D) is an additional layer of authentication designed to protect customers and merchants from fraudulent card transactions. It’s similar to two-factor authentication but specifically for credit and debit card payments.
When 3D Secure is enabled, cardholders may be asked to verify their identity — typically through:
A one-time code sent via SMS or email, or
Logging in to a secure portal provided by their card issuer.
This verification process helps ensure that the person making the payment is the legitimate cardholder.
How 3D Secure Works
The 3DS process runs entirely through the payment gateway, not through Payments2Us directly. When a customer submits payment on a Payments2Us checkout form:
The form sends the transaction to your chosen payment gateway.
If 3DS is enabled and required for that transaction, the gateway redirects the customer to complete verification.
Once the customer completes verification, the gateway confirms the result back to Payments2Us for processing.
Payments2Us itself does not perform 3DS authentication — the feature is managed and controlled by your payment gateway provider.
Why Use 3D Secure?
Enabling 3D Secure helps reduce fraudulent transactions and chargebacks by requiring cardholder verification. Key benefits include:
Improved fraud protection
Compliance with card scheme security standards (e.g. Visa Secure, Mastercard Identity Check)
Reduced liability for unauthorized payments
Gateways Known to Support 3D Secure
The following gateways are confirmed to support or likely support 3D Secure authentication:
Gateway
3DS Support
Stripe SCA
✅ Yes
Windcave (PxPay)
✅ Yes
DataTrans
✅ Yes
Blackbaud
✅ Likely
PayPal
✅ Yes (handled by PayPal directly)
Ezidebit
⚠️ Check with Provider
Authorize.Net
❌ No
Global Payments
❌ No
Windcave (Web Services)
❌ No
NAB Transact
❌ No
⚠️ Note: 3D Secure support can change over time. Please confirm the latest status directly with your gateway provider, as Payments2Us does not control the implementation or enforcement of 3DS.
Common Questions
Q: Can I enable 3DS from within Payments2Us? No. Payments2Us does not manage or enable 3D Secure directly — this is done entirely by your payment gateway.
Q: Will 3DS appear on my checkout form? That depends on your gateway. For example, gateways like Stripe and Windcave PxPay show a popup or redirect during checkout, while others handle it in the background.
Q: Do all transactions require 3DS verification? Not always. The card issuer decides when to trigger 3DS based on transaction risk, card type, and user behavior.
Summary
3D Secure adds an essential security layer for online card transactions. While Payments2Us supports the flow for gateways that provide 3DS, configuration and authentication are managed solely at the payment gateway level. We recommend confirming 3D Secure support directly with your gateway provider before enabling it.
