Connect

You must authenticate yourself to access this document.


Forgot your password?

You haven’t created your account yet? Create your account now!

Create an account now

Access Denied

You do not have access to this content.

Forgot your password?

Submit

Error during the authentification

Unable to authenticate. Please, check your email and your password.

Desjardins Payment Solutions

Please select the type of payment solution for which you wish to create an account:

The Internet payment solutions
The integrated and semi-integrated payment solutions

GO

Old Solution: Integration Guides (without redirection)

Preauthorization cancellation

Preauthorization cancellation represents the second step of the purchase with preauthorization process. The preauthorization cancellation request is simply cancellation by the merchant of the preauthorization, in cases where the sale or the reservation would be cancelled, for example. Once this cancellation has been performed, the purchase is considered to have been cancelled and the customer’s funds have been released.

The preauthorization cancellation 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 cancellation 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 confirm the final status of this transaction.

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

Grow your business

Need Help

Newsletter

Your email will not be published

Subscribe free