Tracking the HPP Session and its Status
Each HPP Session is following a state machine to map the Consumers action to a certain state, which allows any integrator to act depending on the current state. To get the current state, integrators have two way, either by reading the or by using the .
Both system can be used at the same time and it is advised to have a batch running in case there was a loose in communication between systems while the callbacks were sent. As described in the , the callback mechanism will try to reach the integrator system with a retry mechanism, but will stop doing so if your system is not answering after a few times.
HPP Session Lifecycle
|Status name||Final||Status description|
Status descriptionSession is created and Consumer has not entered the Payment Page yet.
Status descriptionConsumer has entered the Payment Page on
Status descriptionConsumer has successfully gotten an Authorization from the Payment system on
Status descriptionConsumer has been declined for the Payment on
Status descriptionConsumer has cancelled the HPP Session on
Status descriptionConsumer has pressed the Back button on
Status descriptionConsumer has encountered an error while paying on
Status descriptionSession was disabled by API Call on the Merchant initiative on
Reading the HPP Session updates by polling an endpoint
You can for example use a polling mechanism to check the status of the session and update your data depending on the payload. Although we suggest that you use the callbacks mechanism.
Getting the HPP Session updates by using the callback mechanism
When an integrator can pass an URL that will be called by our systems whenever the status of the session is updated. This is really handy to create interaction whenever something happens and avoid to have a costly polling mechanism.