P2P Checkout flow

The checkout flow is used for p2p transfers. It requires a logged in user, so it will start of in the auth flow.

URL Path: /flow/p2p

How it works

The checkout flow can be just a few steps, or it can be more. It depends on the current state of the user, client configuration, and query parameters.

It starts with the auth flow, and then appends the following steps.

  • Just password
  • Bank ID verification and P2P agreement check
  • Choose payment method
  • Enter payment details, only shown if user chooses new payment method
  • Two Factor Authentication
  • Process payment
  • Receipt, optional, default enabled

Flow is initiated by path /flow/p2p and require query parameters client_id, redirect_uri and response_type. It also requires the query parameter paylink which must be the paylink code for a valid paylink generated through the Paylink API.

The flow automatically use the login view. This can however be overridden by appending the parameter signup=1 to the url, which will render the signup view instead.

How it looks

Client teaser and Custom CSS is applied to all of the steps. See Flows for more info.


Help us improve

Did you spot an error? Or maybe you just have a suggestion for how we can improve? Leave a comment, or better yet, send us a pull request on GitHub to fix it (in-browser editing, only takes a moment).

History of this page


Do you have questions, or just want to contribute some newly gained insight? Want to share an example? Please leave a comment. SPiD reads and responds to every question. Additionally, your experience can help others using SPiD, and it can help us continuously improve our documentation.