Salesforce Billing Developer Guide
j
No Results
Search Tips:
- Please consider misspellings
- Try different search keywords
Mapping Gateway Response Codes to Salesforce Billing Gateway Statuses
First, let’s look at the values for the payment transaction’s Status field in Salesforce Billing. When your gateway integration sets Status to a value, Salesforce Billing attempts to perform the action listed in the Salesforce Billing Action column in the following table.
| Response | Definition | Salesforce Billing Action |
|---|---|---|
| Success | The gateway call succeeded. | Attempt payment creation and allocation. |
| Decline | The gateway call failed, but it can still work if you try again. For example, the customer had insufficient funds or briefly lost their connection to the internet. This response is also known as a “soft decline.” | Update the payment run’s decline count. Create payment transaction with gateway status of Decline. |
| Validation Error | Customer payment data is incorrect, such a misspelling in the credit card address or incorrect CVV. | Create a payment transaction with a gateway status of Validation Error. |
| Permanent Fail | The gateway call failed and won’t work even if you try again. If you receive this response, don’t make further payments using the related payment method. | Create a payment transaction with a gateway status of Permanent Fail. |
| Requires Review | The customer bank requires additional information before completing the payment. | Create a payment transaction with gateway status of Requires Review. |
| Indeterminate | The gateway didn’t respond to the call. This response usually happens when Salesforce Billing times out waiting for the response. This response doesn’t increase the payment run’s failure count. | Lock the invoice from further payment runs. Create a payment transaction with a gateway status of Indeterminate. Allow users to autovoid or manually create a payment. |
| System Fail | Salesforce Billing ended the payment request call before receiving a response. For example, Salesforce Billing lost credentials or lost access to its server. This response increases the payment run’s failure count. Salesforce Billing ends payment calls if it doesn’t receive a response from the gateway in two minutes. | Create a payment transaction with a gateway status of System Fail. Allow users to autovoid or manually create a payment. |
Response codes and descriptions vary between payment gateway providers. Let’s look at a few examples and see how they can map to a gateway status.
| Gateway | Code | Gateway’s Description | Salesforce Billing Equivalent |
|---|---|---|---|
| Payeezy | 100 | “Approved” | Success |
| CyberSource | 151 |
“The request was received, but a server timeout occurred. This error doesn’t include timeouts between the client and the server.” “To avoid duplicating the transaction, don’t resend the request until you have reviewed the transaction status at the Business Center. See the documentation for your CyberSource client for more information.” |
Indeterminate |
| PayFlowPro | 4 | “Invalid amount format. Use the format '#####.##' Don’t include currency symbols or commas.” | System |
| AuthorizeDotNet | E00057 | “The user doesn’t have permissions to submit requests from a mobile device.” | Fail |