The Payment Initiation Service (PIS) allows you to initiate payments directly from the PSU's bank account through the Open Payments platform, with a variety of supported payment options.
For requests to the PIS API, you need an access token with
scopeset topaymentinitiationcorporate.
Initiating payments in the production environment requires completed KYC verification on the PSU's organization. Refer to the KYC guide for information on how to implement this.
Single Payments
Several different types of single payments can be initiated through the PIS, each identified by a specific payment-product in the endpoint path and with some differences in required parameters. The general flow for initiating a single payment is the same for all except the international-tp product, which includes an additional first step of creating an FX quote.
| payment-product | Flow |
|---|---|
| domestic, swedish-giro, sepa-credit-transfers | Create Payment → Authorise Payment → Get Payment Status |
| international-tp | Create FX Quote → Create Payment → Authorise Payment → Get Payment Status |
0. Create FX Quote (International TP only)
The international-tp product enables you to initiate cross-border payments to 180+ countries with built-in, real-time currency conversion — supporting both spot and forward exchange rates (up to 30 days). The first step for a cross-currency payment is to create an FX quote, defining the exchange rate, fees, and the validity period.
Endpoint
Code
Request Headers
| Name | Type | Description |
|---|---|---|
| X-Request-ID | string(uuid) | The ID of the request, unique to the call, as determined by the initiating party. |
Request Body
| Name | Type | Description |
|---|---|---|
| sourceCurrency | string | The source currency. |
| targetCurrency | string | The target currency. |
| requestedExecutionDate | string(date) | The requested execution date, for future payments. |
| countryCode | string | The target country. |
| amount | string | The requested amount. |
Code
Response
Code
The response contains an fxQuoteId which you will need to reference in the request headers of the international-tp payment request.
1. Create Payment
This step initiates the actual payment. Here, you define the payment instructions according to the selected payment-product.
Domestic
Local account-to-account transfers in the bank's national system.
Endpoint
Code
Request Headers
| Name | Type | Description |
|---|---|---|
| X-Request-ID | string(uuid) | The ID of the request, unique to the call, as determined by the initiating party. |
| X-BicFi | string | The BIC of the bank to which the request is addressed. |
| PSU-ID | string | The ID used to identify the PSU at the bank. Typically a local social security number or another unique login ID. |
| PSU-Corporate-ID | string | The Corporate ID of the PSU when acting on behalf of an organization, e.g. Org. nummer for SE, KVK for NL. |
| TPP-Redirect-Preferred | boolean | Indicates a preference for redirect-based SCA over decoupled when set to true. The bank may not support both types. |
| PSU-IP-Address | string(ipv4) | The IP address of the PSU to be forwarded to the bank. Only included if the request was actively initiated by the PSU. |
| PSU-User-Agent | string | The forwarded Agent header field of the HTTP request between PSU and TPP, if available. |
To try out our harmonized payment statuses, include an X-Feature-Flags header set to new-statuses.
Request Body
| Name | Type | Description |
|---|---|---|
| instructedAmount | object | The amount and currency of the money to be transferred. |
| debtorAccount | object | The account from which the payment will be debited. |
| creditorName | string | The full name of the payment recipient. |
| creditorAccount | object | The account to which the payment will be credited. |
| requestedExecutionDate | string(date) | The date when the payment is scheduled to be executed in ISO 8601 format, e.g. 2025-10-31. |
| remittanceInformationUnstructured | string | A free-text field for remittance information on the payment. |
Code
Swedish Giro
Domestic transfers within Sweden via the Bankgirot and Plusgirot systems.
Endpoint
Code
Request Headers
| Name | Type | Description |
|---|---|---|
| X-Request-ID | string(uuid) | The ID of the request, unique to the call, as determined by the initiating party. |
| X-BicFi | string | The BIC of the bank to which the request is addressed. |
| PSU-ID | string | The ID used to identify the PSU at the bank. Typically a local social security number or another unique login ID. |
| PSU-Corporate-ID | string | The Corporate ID of the PSU when acting on behalf of an organization, e.g. Org. nummer for SE, KVK for NL. |
| TPP-Redirect-Preferred | boolean | Indicates a preference for redirect-based SCA over decoupled when set to true. The bank may not support both types. |
| PSU-IP-Address | string(ipv4) | The IP address of the PSU to be forwarded to the bank. Only included if the request was actively initiated by the PSU. |
| PSU-User-Agent | string | The forwarded Agent header field of the HTTP request between PSU and TPP, if available. |
Request Body
| Name | Type | Description |
|---|---|---|
| instructedAmount | object | The amount and currency of the money to be transferred. |
| debtorAccount | object | The account from which the payment will be debited. |
| creditorName | string | The full name of the payment recipient. |
| creditorGiro | object | The Bankgirot or Plusgirot account to which the payment will be credited. |
| requestedExecutionDate | string(date) | The date when the payment is scheduled to be executed in ISO 8601 format, e.g. 2025-10-31. |
| invoiceRef | string | A custom invoice reference. |
| ocrRef | string | A Giro OCR reference. |
Code
International TP
Cross-border payments using FX quotes.
Endpoint
Code
Request Headers
| Name | Type | Description |
|---|---|---|
| X-Request-ID | string(uuid) | The ID of the request, unique to the call, as determined by the initiating party. |
| X-BicFi | string | The BIC of the bank to which the request is addressed. |
| PSU-ID | string | The ID used to identify the PSU at the bank. Typically a local social security number or another unique login ID. |
| PSU-Corporate-ID | string | The Corporate ID of the PSU when acting on behalf of an organization, e.g. Org. nummer for SE, KVK for NL. |
| TPP-Redirect-Preferred | boolean | Indicates a preference for redirect-based SCA over decoupled when set to true. The bank may not support both types. |
| PSU-IP-Address | string(ipv4) | The IP address of the PSU to be forwarded to the bank. Only included if the request was actively initiated by the PSU. |
| PSU-User-Agent | string | The forwarded Agent header field of the HTTP request between PSU and TPP, if available. |
| FX-Quote-Id | string | The ID of the FX Quote to be used for the payment. Used for international TP payments only. |
Request Body
| Name | Type | Description |
|---|---|---|
| instructedAmount | object | The amount and currency of the money to be transferred. |
| debtorAccount | object | The account from which the payment will be debited. |
| creditorName | string | The full name of the payment recipient. |
| creditorAccount | object | The account to which the payment will be credited. |
| creditorAddress | object | The address of the payment recipient. |
| creditorAgent | string | The BIC of the payment recipient's bank. |
| creditorAgentName | string | The name of the payment recipient's bank. |
| requestedExecutionDate | string(date) | The date when the payment is scheduled to be executed in ISO 8601 format, e.g. 2025-10-31. |
| remittanceInformationUnstructured | string | A free-text field for remittance information on the payment. |
Code
The payment needs to be signed within one hour of creating the FX quote. If the payment does not reach a finalised state within this timeframe, the FX contract will be voided and a new quote will need to be created.
SEPA Credit Transfers
Payments in EUR between accounts in the SEPA (Single Euro Payments Area) zone.
Endpoint
Code
Request Headers
| Name | Type | Description |
|---|---|---|
| X-Request-ID | string(uuid) | The ID of the request, unique to the call, as determined by the initiating party. |
| X-BicFi | string | The BIC of the bank to which the request is addressed. |
| PSU-ID | string | The ID used to identify the PSU at the bank. Typically a local social security number or another unique login ID. |
| PSU-Corporate-ID | string | The Corporate ID of the PSU when acting on behalf of an organization, e.g. Org. nummer for SE, KVK for NL. |
| TPP-Redirect-Preferred | boolean | Indicates a preference for redirect-based SCA over decoupled when set to true. The bank may not support both types. |
| PSU-IP-Address | string(ipv4) | The IP address of the PSU to be forwarded to the bank. Only included if the request was actively initiated by the PSU. |
| PSU-User-Agent | string | The forwarded Agent header field of the HTTP request between PSU and TPP, if available. |
Request Body
| Name | Type | Description |
|---|---|---|
| instructedAmount | object | The amount and currency of the money to be transferred. |
| debtorAccount | object | The account from which the payment will be debited. |
| creditorName | string | The full name of the payment recipient. |
| creditorAccount | object | The account to which the payment will be credited. |
| creditorAgent | string | The BIC of the payment recipient's bank. |
| creditorAgentName | string | The name of the payment recipient's bank. |
| requestedExecutionDate | string(date) | The date when the payment is scheduled to be executed in ISO 8601 format, e.g. 2025-10-31. |
| remittanceInformationUnstructured | string | A free-text field for remittance information on the payment. |
Code
Response
Code
If the creditor account is listed on Svensk Handel's watchlist, the response will additionally contain the following warning message:
Code
If the creditor account has OCR reference validation enabled and the provided OCR reference is invalid, the response will additionally contain the following warning message:
Code
2. Authorise Payment
After creating the payment, it must be authorised by the PSU before it can be used. See the Authorisations guide for instructions on how to complete the authorisation process.
3. Get Payment Status
Once you complete the authorisation flow, check the status of the payment by polling the Get Payment Status endpoint.
Endpoint
Code
Path Parameters
| Name | Type | Description |
|---|---|---|
| payment-service | string | The type of payment to initiate, e.g. payments for single payments. |
| payment-product | string | The scheme and format of the payment, e.g. domestic for domestic payments. |
| paymentId | string(uuid) | The ID of the payment that was created. |
Request Headers
| Name | Type | Description |
|---|---|---|
| X-Request-ID | string(uuid) | The ID of the request, unique to the call, as determined by the initiating party. |
| X-BicFi | string | The BIC of the bank to which the request is addressed. |
| PSU-ID | string | The ID used to identify the PSU at the bank. Typically a local social security number or another unique login ID. |
| PSU-Corporate-ID | string | The Corporate ID of the PSU when acting on behalf of an organization, e.g. Org. nummer for SE, KVK for NL. |
| TPP-Redirect-Preferred | boolean | Indicates a preference for redirect-based SCA over decoupled when set to true. The bank may not support both types. |
| PSU-IP-Address | string(ipv4) | The IP address of the PSU to be forwarded to the bank. Only included if the request was actively initiated by the PSU. |
| PSU-User-Agent | string | The forwarded Agent header field of the HTTP request between PSU and TPP, if available. |
Code
Response
Code
Payments can have a number of different statuses. Here, you want to check if the payment was rejected, in which case transactionStatus would have the value RJCT. If not, then you are done.
Signing Baskets
Alternatively to authorising each payment separately, signing baskets allow several initiated payments to be grouped and authorised in a single SCA flow. Once a signing basket is signed, each payment within it is signed simultaneously, ensuring consistency and reducing friction. All supported payment types can be included in a signing basket.
1. Create Signing Basket
After creating the desired payments as described above, you can create a signing basket and include each paymentId in the request body.
Endpoint
Code
Request Headers
| Name | Type | Description |
|---|---|---|
| X-Request-ID | string(uuid) | The ID of the request, unique to the call, as determined by the initiating party. |
| X-BicFi | string | The BIC of the bank to which the request is addressed. |
| PSU-ID | string | The ID used to identify the PSU at the bank. Typically a local social security number or another unique login ID. |
| PSU-Corporate-ID | string | The Corporate ID of the PSU when acting on behalf of an organization, e.g. Org. nummer for SE, KVK for NL. |
| TPP-Redirect-Preferred | boolean | Indicates a preference for redirect-based SCA over decoupled when set to true. The bank may not support both types. |
| PSU-IP-Address | string(ipv4) | The IP address of the PSU to be forwarded to the bank. Only included if the request was actively initiated by the PSU. |
| PSU-User-Agent | string | The forwarded Agent header field of the HTTP request between PSU and TPP, if available. |
Request Body
| Name | Type | Description |
|---|---|---|
| paymentIds | array | The IDs of the payments to include in the signing basket. |
Code
2. Authorise Signing Basket
After creating the signing basket, it must be authorised by the PSU. See the Authorisations guide for instructions on how to complete the authorisation process.
3. Get Signing Basket Status
Once you complete the authorisation flow, check the status of the payment by polling the Get Signing Basket Status endpoint.
Endpoint
Code
Path Parameters
| Name | Type | Description |
|---|---|---|
| basketId | string | The ID of the signing basket that was created. |
Request Headers
| Name | Type | Description |
|---|---|---|
| X-Request-ID | string(uuid) | The ID of the request, unique to the call, as determined by the initiating party. |
| X-BicFi | string | The BIC of the bank to which the request is addressed. |
| PSU-ID | string | The ID used to identify the PSU at the bank. Typically a local social security number or another unique login ID. |
| PSU-Corporate-ID | string | The Corporate ID of the PSU when acting on behalf of an organization, e.g. Org. nummer for SE, KVK for NL. |
| TPP-Redirect-Preferred | boolean | Indicates a preference for redirect-based SCA over decoupled when set to true. The bank may not support both types. |
| PSU-IP-Address | string(ipv4) | The IP address of the PSU to be forwarded to the bank. Only included if the request was actively initiated by the PSU. |
| PSU-User-Agent | string | The forwarded Agent header field of the HTTP request between PSU and TPP, if available. |
Code
Response
Code
Signing baskets can have a number of different statuses. Here, you want to check if the basket was rejected, in which case transactionStatus would have the value RJCT. If not, then you are done.
Also verify each included payment's status via the Get Payment Status endpoint regardless of the signing basket's scaStatus.

