List of Messages

Messages go in both directions (between the library and SagePay site, as initiating requests and callbacks). Each message is a POST, and has parameters. Each POST has a response, and that also has parameters. This page aims to list those messages so that we can:

1. Give each message a name.
2. Update the metadata with details of the parameters.

Documentation from SagePay is spread over a number of sections of multiple documents. We would like to gather it all together in one place (the metadata file) so that the raw data can help drive the processes with the minimum of hard-coding.

SagePay Server

This method uses the fewest messages.

TODO

SagePay Direct

In theory this should involve fewer messages as there should be less reason to send the user to third-party sites. However, with 3DSecure and SagePay redirects then being pulled into the application, rather than being handled by SagePay in a single call - effectively wrapping that functionality up into a black box - the SagePay Direct method involves many more messages.

TODO

Shared Method Messages

A handful of messages are used by both SagePay Server and SagePay Direct, and operate in the same way for both methods.

TODO