Old Solution: Integration Guides (without redirection)

Preauthorization

Preauthorization is, in effect, a two-phase purchase transaction. For example, it could involve a purchase that will only be completed when the merchant delivers the order to the client or it could involve a reservation on a hotel industry website.

The preauthorization allows for « holding » the transaction amount without having to complete the transaction immediately and thus be able to refund the amount if the transaction would need to be cancelled. The preauthorization duration (before its cancellation and the release of the held funds) varies according to the card issuer’s policies.

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

Phase A: (beginning)

The merchant’s communications module acts as client for the first three (3) steps, it initiates the communications with the Desjardins secure payment server in order to open a session and send the transaction related 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.

Phase B:

The merchant’s communications module acts as server for the next 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 4 and step 6 XML requests are received in the HTTPS message body via a POST and contain content type “text/xml” in their header.

The preauthorized purchase must subsequently be either confirmed or cancelled.

Phase A: (end)

The final step (step 8) contains a message that closes the initial request. The message is a final response to the preauthorization request. It uses the connection that was made in step 3 of Phase A.

See the steps