This article explains what this error means, the common causes behind it, and how to resolve or troubleshoot the issue.
If you see the message:
“Payment Failed – Gateway Error (IO Exception – Unable to tunnel through proxy. Proxy returns HTTP/1.1 503 Service Unavailable)”
It means that Payments2Us could not connect to your payment gateway at that moment.
This is typically caused by:
- A temporary outage at the payment gateway
- A timeout or degraded gateway performance
- Incorrect Payments2Us or Salesforce configuration
In most cases, this is a temporary issue that resolves automatically once the gateway connection is restored.
What to Do
-
Check Your Gateway’s Status Page
Review your payment gateway’s status for outages or maintenance.
You can find the list of supported gateways here: Gateway Status Links. -
Confirm the Payment Outcome
If the payment appears as “failed” in Payments2Us, check your gateway’s portal to verify if it was actually processed.
If successful in the gateway, wait for the next automatic retry, or manually update the transaction record in Payments2Us. -
Review Configuration Settings
Ensure that Salesforce and Payments2Us are configured to allow outbound HTTPS/API calls to your payment gateway.
Review: Payments2Us Security and Configuration. -
Contact Your Gateway Provider
If the problem continues, contact your payment gateway’s support team to confirm whether there was an outage or technical issue on their end.
Error Details
| Program/Area: | CheckoutCon.payNow |
| Subject: | Checkout Error (Timeout Error) |
| Description: | Payments2Us was unable to connect to your payment gateway during processing. This usually indicates a temporary connectivity or response issue between Salesforce/Payments2Us and your gateway’s API. |
Possible Causes
-
Temporary Payment Gateway Outage
The payment gateway may be undergoing scheduled maintenance or facing temporary downtime. Check its status page for updates. -
Gateway Busy or Timed Out
The gateway may have been too busy to respond to the API request, resulting in a “503 Service Unavailable” message. -
Salesforce Configuration or API Issue
If the Payments2Us configuration within Salesforce is misconfigured (e.g., incorrect endpoint, blocked proxy, or security restriction), Salesforce might not reach the gateway, leading to this error. -
Bank or Processor Downtime
Occasionally, the issue may stem from the bank or financial processor linked to your gateway. If the payer’s bank is experiencing downtime or connection issues, the gateway might not complete the transaction.
Recommended Steps
-
Check the Gateway Status
Confirm whether the gateway is operational.
For reference, see: Payment Gateway Status Links. -
Verify the Payment Directly in the Gateway
For recurring payments, check the transaction’s status within the gateway itself.
If successful there but failed in Payments2Us, manually mark the record or wait for the automatic retry. -
Wait for Automatic Retry
Payments2Us automatically retries failed payments four times a day (every six hours).- If the retry is successful, the transaction status will update to “Confirmed - Checked” or “Matching Complete”.
- If the transaction fails again due to payer-related issues (e.g., insufficient funds), the status will show “Error - Checked”.
-
Review and Confirm Configuration
If errors persist, ensure outbound HTTPS/API requests are not blocked.
Review your setup with your Salesforce Admin or implementation partner:- Security and Controls
- Installation Security Settings
Conclusion / Additional Notes
- This error does not always indicate a failed payment — it often means Payments2Us couldn’t confirm the result at that time.
- In many cases, Payments2Us automatically reconciles the payment once communication with the gateway resumes.
- If the issue persists, contact your payment gateway’s support for further assistance.