Payment initiation

STET PSD2 API

STET payment request and confirmation

The French profile. Two calls that matter: create the payment request, then confirm it after SCA. Skipping the confirmation is the single most common STET bug.

Why read this

Any PISP operating in France. The HTTP Signature requirement makes this the least forgiving standard to debug.

Samples in this flow

Try in live showcase

pispstetfrancehttp signature

Transaction flow

PSUUserTPPProviderASPSPBankSCAAuth01 Get a client_credentials token01 POST02 Create the payment request02 POST03 Authenticate via the consentApprovalUrl0304 Confirm the payment request04 POST05 Read the final status05 GET
PSU: UserTPP: ProviderASPSP: BankSCA: Auth
API hop Clearing hopClick a tag on an arrow (pacs.008, …) for info, usage and sample
01

Get a client_credentials token

API layer

POST/oauth2/token→ 200

grant_type=client_credentials with scope=pisp. The token is bound to the QWAC used for mTLS.

Codes you can see here

invalid_clientinvalid_scope

tppaspsp

No payload

This step is a redirect, a wait or an out-of-band event — there is no message on the wire to inspect. Steps with a payload are marked with a method or a message id in the diagram.

See this step in live →