Using the External Option to Create Links to Other Gateways

Integrators can create links to other (external) credit card gateways. To set this up:

1. SSSCCIProcessCardExternalSp is a stored procedure that calls your extension procedure EXTSSSCCIProcessCardExternalSp, if it exists. Look in SSSCCIProcessCardExternalSp to see what parameters are being passed to the extension procedure.
2. Create the extension procedure named EXTSSSCCIProcessCardExternalSp to handle processing to the external gateway, using the parameters passed from SSSCCIProcessCardExternalSp. Add this stored procedure to the application database.
3. Select the External option on the Credit Card Interface Parameters form so that, during credit card processing, the application checks for the existence of your extension procedure and calls it, if it exists.
4. See Setting Up the Credit Card Interface for additional steps to perform on the Credit Card Interface Parameters form.

   Note: On this form, specify the external gateway user ID and password credentials and the URL for the target web service. If these values are not set up, then when users try to authorize a credit card payment for an order, a message informs them that Credit Card Interface Parameters are required.

The Credit Card System list can be specialized with an inline list value that is more descriptive than External, to better describe the actual target gateway. The logic in the middle and back-end layer executes the external logic when the value is something other than Hypercom, Intrix, or TGate.

For External gateways, the integrator must determine security. This application does not encrypt the password on the Credit Card Interface Parameters form for these external gateways. If an integrator requires a password to be encrypted or additional setup information for the external gateway, use UETs and form personalizations to acquire that information.