Old Solution: Integration Guides (without redirection)

Preauthorization completion

Preauthorization completion represents the second step of the purchase with preauthorization process. Once this step is successfully completed, the purchase is considered to have been completed. The amount is debited from the customer’s credit card and the funds are credited to the merchant’s account.

The preauthorization completion process is made up of 2 phases containing 4 steps each.

Phase A:

The merchant’s communications module acts as client for the first four (4) steps, it initiates the communications with the Desjardins secure payment server in order to open a session and to send the transaction information.

The step 1 and step 3 XML requests must be sent in the HTTPS message body via a POST and must contain content type “text/xml” in their header.

Following successful execution of the Phase A steps, the preauthorization completion request will be processed in batch, involving a maximum delay of (2) minutes. Phase B then is the response sent by the Desjardins secure payment server to the merchant’s communications module.

Phase B:

The merchant’s communications module acts as server for the final four (4) steps, the Desjardins secure payment server initiating the communication with the module in order to return the current transaction status and to confirm the final transaction status.

The step 5 and step 7 XML requests are received in the HTTPS message body via a POST and contain content type “text/xml” in their header.

See the steps