Submit scheme selection

Submit the scheme details selected by the PSU

This API can be called:

  • using the resource_token associated with the payment you are trying to authorize;
  • using a backend bearer token.
📘

Endpoint path changes

All Payments API v3 endpoints now start with /v3/. The old endpoints still work, but you must use the new path for all new integrations.

Path Params
string
required

ID of the payment

Body Params
string
required

The id of the scheme to make the payment over.

Headers
string

An idempotency key to allow safe retrying without the operation being performed multiple times.
The value should be unique for each operation (we strongly advise to use a UUID v4), with the same key being sent on a retry of the same request.

string

A JWS with detached content, signed with your private key.
See Request Signing.

Required with a OAuth2 token.

string
enum
Defaults to application/json; charset=UTF-8

Generated from available response content types

Allowed:
Responses

Language
Credentials
URL
Response
Choose an example:
application/json; charset=UTF-8
application/problem+json; charset=UTF-8