Understanding the Response
If you receive any errors from eWAY, or for more information about the eWAY responses that are saved in the Chargent Transaction record in Salesforce, please see the eWAY Response Codes.
All the data in the Chargent Transaction record in Salesforce comes from eWAY (except for the Transaction name, beginning with TRX-000XXX, which is autogenerated). For more information please see the documentation on Chargent Transactions.
Complete any additional Salesforce configuration your organization requires
Once you are generating responses from eWAY and seeing the transaction records, you may wish to finalize other Salesforce configuration items, such as:
- Email receipts from Salesforce and/or eWAY
- Automated processes in Salesforce driven by transactions
- Other requirements of your organization
Sending Live Transactions from a Salesforce Sandbox
When Chargent is installed in a Salesforce Sandbox, transactions are always sent to the payment gateway’s test / sandbox / development environment, regardless of whether Chargent’s Test Endpoint checkbox is checked. This is done as a security precaution, to prevent real transactions from being accidentally sent from a Salesforce Sandbox.
When Chargent is installed in a production or developer Salesforce org, the Test Endpoint checkbox on the Gateway record will select between sending to the payment gateway’s live and test environments.
If you wish to send live transactions from a Salesforce Sandbox, as a final step in testing, simply use Chargent’s Endpoint Override field on the Gateway record, and enter the production endpoint of your chosen gateway there.
Here is the production endpoint URL for Chargent’s integration with eWAY:
Note that the full endpoint URL must be entered in the Endpoint Override field, and the domain must be present in the Remote Site Settings (for standard Chargent integrations it should be already present).