About Swish
General information about Swish
Logo |
|
Info | The swedish payment method Swish is one of the most popular payment methods in Sweden. More than half of the population uses the app on their cell phones. Originally Swish was a joint venture project of the most popular swedish banks as a pure P2P-payment method. Since 2017 it is also available for E-Commerce and POS. If you want to pay, you can either do it via scan of a QR-code or the submission of your mobile or swish number. |
Type |
Further information can be found on the webpage of Swish (https://www.swish.nu/).
Process flow charts
Process flow E-Commerce checkout with Swish
Process flow M-Commerce checkout with Swish
Configuration for Swish
Certificate Management
Each merchant needs a certificate for each MID. For the Certificate Management, you need to download the following document: https://developer.swish.nu/documentation/integration
You need to order a new Certificate, as described in section 2.6 of the downloaded document. The Certificate Signing Request (CSR) will be provided by Computop.
Overview of the Certificate Management process:
Once you have access to Swish Certificate Management Tool, contact Computop at Computop Helpdesk with request for Swish CSR
Computop creates CSR and sends it to you
You will need to upload the CSR received from Computop in Swish Certificate Management Tool
You will generate and download the Certificate, as described in section 2.6 of the downloaded document. The format of Certificate can be either PEM or PKCS#7.
You will send back to Computop the Certificate as response to email with CSR received from Computop
Paygate interface
Definitions
Data formats
Format | Description |
a | alphabetical |
as | alphabetical with special characters |
n | numeric |
an | alphanumeric |
ans | alphanumeric with special characters |
ns | numeric with special characters |
bool | boolean expression (true or false) |
3 | fixed length with 3 digits/characters |
..3 | variable length with maximum 3 digits/characters |
enum | enumeration of allowed values |
dttm | ISODateTime (YYYY-MM-DDThh:mm:ss) |
Abbreviations
Abbreviation | Description | Comment |
CND | condition | |
M | mandatory | If a parameter is mandatory, then it must be present |
O | optional | If a parameter is optional, then it can be present, but it is not required |
C | conditional | If a parameter is conditional, then there is a conditional rule which specifies whether it is mandatory or optional |
Notice: Please note that the names of parameters can be returned in upper or lower case.
Call of interface for Swish
In order to process a Swish payment via the Paygate form, please use the following URL:
https://www.computop-paygate.com/swish.aspx
Notice: For security reasons, Computop Paygate rejects all payment requests with formatting errors. Therefore, please use the correct data type for each parameter.
The following table describes the encrypted payment request parameters:
| Key | Format | CND | Description |
|---|---|---|---|
ans..30 | M | MerchantID, assigned by Computop. Additionally this parameter has to be passed in plain language too. | |
ans..64 | M | TransactionID provided by you which should be unique for each payment | |
RefNr | ans..35 | O | Unique reference number |
Amount | n..10 | M | Amount in the smallest currency unit (e.g. SEK Öre). Please contact the helpdesk, if you want to capture amounts < 100 (smallest currency unit). |
Currency | a3 | M | Currency, three digits DIN / ISO 4217. Only SEK permitted. |
an64 | M | Hash Message Authentication Code (HMAC) with SHA-256 algorithm. Details can be found here: | |
OrderDesc | ans..128 | M | Description of purchased goods, unit prices etc. Permitted characters a-ö, A-Ö, the digits 0-9 and the special characters :;.,?!()”. |
ans..32 | O | To avoid double payments or actions (e.g. by ETM), enter an alphanumeric value which identifies your transaction and may be assigned only once. If the transaction or action is submitted again with the same ReqID, Computop Paygate will not carry out the payment or new action, but will just return the status of the original transaction or action. Please note that the Computop Paygate must have a finalized transaction status for the first initial action (authentication/authorisation). This does not apply to 3-D Secure authentications that are terminated by a timeout. The 3-D Secure Timeout status does not count as a completed status in which the ReqID functionality on Paygate does not take effect. Submissions with identical ReqID for an open status will be processed regularly. Notice: Please note that a ReqID is only valid for 12 month, then it gets deleted at the Paygate. | |
Channel | a3 | M | Channel for processing the payment Possible values: Web or App Web = eCommerce App = mCommerce |
MobileNr | n..20 | C | Customer’s mobile telephone number. (mandatory if Channel = Web) The submitted mobile telephone number of that person that makes the payment. Only digits are allowed and it must have at least 8 digits and maximal 15 digits. In order to get found by Swish, it also must comply with the following format: Country code + Mobile telephone number (without leading Zero). e.g.: 46712345678 |
ans..256 | M | Complete URL which Paygate calls up in order to notify the shop about the payment result. The URL may be called up only via port 443. It may not contain parameters: Use the UserDataparameter instead. Common notes:
| |
ans..1024 | O | If specified at request, Paygate forwards the parameter with the payment result to the shop. |
Parameters for payments with Swish
The following table describes the result parameters with which the Computop Paygate responds to your system
pls. be prepared to receive additional parameters at any time and do not check the order of parameters
the key (e.g. MerchantId, RefNr) should not be checked case-sentive
| Key | Format | CND | Description |
|---|---|---|---|
ans..30 | M | MerchantID, assigned by Computop | |
an32 | M | ID assigned by Paygate for the payment, e.g. for referencing in batch files as well as for capture or credit request. | |
an32 | M | ID for all single transactions (authorisation, capture, credit note) for one payment assigned by Paygate | |
ans..64 | M | TransactionID provided by you which should be unique for each payment | |
RefNr | ans..35 | O | Unique reference number |
Status | a..50 | M | AUTHORIZE_REQUEST or FAILED |
ans..1024 | M | Further details in the event that payment is rejected. Please do not use the Description but the Code parameter for the transaction status analysis! | |
an8 | M | Error code according to Paygate Response Codes (A4 Error codes) | |
CodeExt | ans..10 | C | Error code from Swish. Notice: Is returned only if Status=FAILED. Use is possible only in agreement with Computop Helpdesk. |
ErrorText | ans..256 | C | Detailed Swish error message. Notice: Is returned only if Status=FAILED. Use is possible only in agreement with Computop Helpdesk. |
TransactionID | ans..50 | O | Transaction ID from Swish |
TokenExt | an..32 | C | In order to open the Swish app TokenExt together with the Custom URL Scheme are necessary. TokenExt ist returned only if Channel=App. e.g..: swish://paymentrequest?token=f34DS34lfd0d03fdDselkfd3ffk21 |
URLConfirm | ans..256 | O | Location URL returned by Swish. e.g.: https://mss.swicpc.bankgirot.se/swish-cpcapi/api/v1/paymentrequests/A44C22F42E3C4D498C4D8B1D4A6CE743 |
ans..1024 | O | If specified at request, Paygate forwards the parameter with the payment result to the shop. |
Result parameters for Swish payments
The following table gives the results parameters which the Paygate transfers to your URLNotify. If you have specified the Response=encrypt parameter, the following parameters are sent Blowfish encrypted to your system:
| Key | Format | CND | Description |
|---|---|---|---|
ans..30 | M | MerchantID, assigned by Computop | |
an32 | M | ID assigned by Paygate for the payment, e.g. for referencing in batch files as well as for capture or credit request. | |
an32 | M | ID for all single transactions (authorisation, capture, credit note) for one payment assigned by Paygate | |
ans..64 | M | TransactionID provided by you which should be unique for each payment | |
RefNr | ans..35 | O | Unique reference number |
a..50 | M | OK (URLSuccess) or FAILED (URLFailure) | |
ans..1024 | M | Further details in the event that payment is rejected. Please do not use the Description but the Code parameter for the transaction status analysis! | |
an8 | M | Error code according to Paygate Response Codes (A4 Error codes) | |
CodeExt | ans..10 | C | Error code from Swish. Notice: Is returned only if Status=FAILED. Use is possible only in agreement with Computop Helpdesk. |
ErrorText | ans..256 | C | Detailed Swish error message. Notice: Is returned only if Status=FAILED. Use is possible only in agreement with Computop Helpdesk. |
TransactionID | ans..50 | O | Transaction ID from Swish |
TokenExt | an..32 | C | In order to open the Swish app TokenExt together with the Custom URL Scheme are necessary. TokenExt ist returned only if Channel=App. e.g..: swish://paymentrequest?token=f34DS34lfd0d03fdDselkfd3ffk21 |
URLConfirm | ans..256 | O | Location URL returned by Swish. e.g.: https://mss.swicpc.bankgirot.se/swish-cpcapi/api/v1/paymentrequests/A44C22F42E3C4D498C4D8B1D4A6CE743 |
ans..1024 | O | If specified at request, Paygate forwards the parameter with the payment result to the shop. |
Result parameters for URLNotify
Credit with reference
Credits (refunds) are possible via a Server-to-Server connection. For a Credit with reference to a capture the amount of the Credit is limited to the amount of the previous capture. To carry out a credit with a reference transaction, please use the following URL:
https://www.computop-paygate.com/credit.aspx
Notice: For security reasons, Computop Paygate rejects all payment requests with formatting errors. Therefore, please use the correct data type for each parameter.
The following table describes the encrypted payment request parameters:
| Key | Format | CND | Description |
|---|---|---|---|
ans..30 | M | MerchantID, assigned by Computop. Additionally this parameter has to be passed in plain language too. | |
an32 | M | ID assigned by Paygate for the payment to be credited | |
ans..64 | M | TransactionID provided by you which should be unique for each payment | |
RefNr | ans..35 | O | Unique reference number |
Amount | n..10 | M | Amount in the smallest currency unit (e.g. SEK Öre). Please contact the helpdesk, if you want to capture amounts < 100 (smallest currency unit). |
Currency | a3 | M | Currency, three digits DIN / ISO 4217. Only SEK permitted. |
an64 | M | Hash Message Authentication Code (HMAC) with SHA-256 algorithm. Details can be found here: | |
ans..32 | O | To avoid double payments or actions (e.g. by ETM), enter an alphanumeric value which identifies your transaction and may be assigned only once. If the transaction or action is submitted again with the same ReqID, Computop Paygate will not carry out the payment or new action, but will just return the status of the original transaction or action. Please note that the Computop Paygate must have a finalized transaction status for the first initial action (authentication/authorisation). This does not apply to 3-D Secure authentications that are terminated by a timeout. The 3-D Secure Timeout status does not count as a completed status in which the ReqID functionality on Paygate does not take effect. Submissions with identical ReqID for an open status will be processed regularly. Notice: Please note that a ReqID is only valid for 12 month, then it gets deleted at the Paygate. |
Parameters for credits of Swish payments
The following table describes the result parameters with which the Computop Paygate responds to your system
pls. be prepared to receive additional parameters at any time and do not check the order of parameters
the key (e.g. MerchantId, RefNr) should not be checked case-sentive
| Key | Format | CND | Description |
|---|---|---|---|
ans..30 | M | MerchantID, assigned by Computop | |
an32 | M | ID assigned by Paygate for the payment, e.g. for referencing in batch files as well as for capture or credit request. | |
an32 | M | ID for all single transactions (authorisation, capture, credit note) for one payment assigned by Paygate | |
ans..64 | M | TransactionID provided by you which should be unique for each payment | |
RefNr | ans..35 | O | Unique reference number |
a..50 | M | OK (URLSuccess) or FAILED (URLFailure) | |
ans..1024 | M | Further details in the event that payment is rejected. Please do not use the Description but the Code parameter for the transaction status analysis! | |
an8 | M | Error code according to Paygate Response Codes (A4 Error codes) |
Result parameters for credits of Swish payments
Reversal
Reversals are possible via a Server-to-Server connection. In order to cancel a payment via a server-to-server communication, please use the following URL:
https://www.computop-paygate.com/reverse.aspx
Notice: For security reasons, Computop Paygate rejects all payment requests with formatting errors. Therefore, please use the correct data type for each parameter.
The following table describes the encrypted payment request parameters:
| Key | Format | CND | Description |
|---|---|---|---|
ans..30 | M | MerchantID, assigned by Computop. Additionally this parameter has to be passed in plain language too. | |
an32 | M | ID assigned by Paygate for the payment to be reversed | |
ans..64 | M | TransactionID provided by you which should be unique for each payment | |
RefNr | ans..35 | O | Unique reference number |
Amount | n..10 | M | Amount in the smallest currency unit (e.g. SEK Öre). Please contact the helpdesk, if you want to capture amounts < 100 (smallest currency unit). |
Currency | a3 | M | Currency, three digits DIN / ISO 4217. Only SEK permitted. |
an64 | M | Hash Message Authentication Code (HMAC) with SHA-256 algorithm. Details can be found here: | |
ans..32 | O | To avoid double payments or actions (e.g. by ETM), enter an alphanumeric value which identifies your transaction and may be assigned only once. If the transaction or action is submitted again with the same ReqID, Computop Paygate will not carry out the payment or new action, but will just return the status of the original transaction or action. Please note that the Computop Paygate must have a finalized transaction status for the first initial action (authentication/authorisation). This does not apply to 3-D Secure authentications that are terminated by a timeout. The 3-D Secure Timeout status does not count as a completed status in which the ReqID functionality on Paygate does not take effect. Submissions with identical ReqID for an open status will be processed regularly. Notice: Please note that a ReqID is only valid for 12 month, then it gets deleted at the Paygate. |
Parameters for reversals with Swish via socket connection
The following table describes the result parameters with which the Computop Paygate responds to your system
pls. be prepared to receive additional parameters at any time and do not check the order of parameters
the key (e.g. MerchantId, RefNr) should not be checked case-sentive
| Key | Format | CND | Description |
|---|---|---|---|
ans..30 | M | MerchantID, assigned by Computop | |
an32 | M | ID assigned by Paygate for the payment, e.g. for referencing in batch files as well as for capture or credit request. | |
an32 | M | ID for all single transactions (authorisation, capture, credit note) for one payment assigned by Paygate | |
ans..64 | M | TransactionID provided by you which should be unique for each payment | |
RefNr | ans..35 | O | Unique reference number |
a..50 | M | OK (URLSuccess) or FAILED (URLFailure) | |
ans..1024 | M | Further details in the event that payment is rejected. Please do not use the Description but the Code parameter for the transaction status analysis! | |
an8 | M | Error code according to Paygate Response Codes (A4 Error codes) |
Response parameters for reversals with Swish via socket connection
Batch processing via the interface
Basic information about using Batch files and about their structure can be found in the Batch Manager manual. Within batch processing not alle functions are available which are usually available for the online interface.
This section describes the parameters which must be transferred within the data set (Record) for executing credits with Swish, which can be found within the response file about the payment status.
Following table gives an overview of all batch versions that are possible for a specific action and their specialities:
Action | Version | Description |
Credit | 1.0 / 2.0 | Standard version without return of parameter Code |
1.x / 2.x | with RefNr (valid for all versions other than 1.0) |
Description of the possible batch versions
The structure for a Swish payment in a Batch file to be submitted is as follows:
1HEAD,<MerchantID>,<Date>,<Version>2Swish,Credit,<Amount>,<Currency>,<TransID>,(<RefNr>,)<PayID>3Swish,Reverse,<Amount>,<Currency>,<TransID>,(<RefNr>,)<PayID>4FOOT,<CountRecords>,<SumAmount>Example for Master MID function:
1HEAD,[Master]MerchantID,Date,2.x2Type,Action,[Slave]MID,Amount,Currency,TransID,Data (depends on Action)3FOOT,CountRecords,SumAmountThe following table describes the individual fields and values used within the data set (record) in the batch file:
| Key | Format | CND | Description |
|---|---|---|---|
Type | a..11 | M | HEAD for Header, FOOT for Footer, Swish for Swish |
Action | a..20 | M | The parameter Action defines the type of transaction: Credit |
Amount | n..10 | M | Amount in the smallest currency unit (e.g. SEK Öre). Please contact the helpdesk, if you want to capture amounts < 100 (smallest currency unit). |
Currency | a3 | M | Currency, three digits DIN / ISO 4217. Only SEK permitted. |
ans..64 | M | TransactionID provided by you which should be unique for each payment | |
RefNr | ans..35 | O | Unique reference number |
an32 | M | ID assigned by Paygate for this transaction |
Description of fields within the record for Batch files
The record area within the response file for Batch transactions looks as follows:
1HEAD,<MerchantID>,<Date>,<Version>2Swish,Credit,<Amount>,<Currency>,<TransID>,(<RefNr>,)<PayID>,<Status>,<Code>3Swish,Reverse,<Amount>,<Currency>,<TransID>,(<RefNr>,)<PayID>,<Status>,<Code>4FOOT,<CountRecords>,<SumAmount>The following table describes the response parameters which the Batch Manager saves in the Record area for each transaction (standard parameters not explained here, such as <TransID> or <RefNR> and request parameters are returned unchanged and correspond to the call as specified before):
| Key | Format | CND | Description |
|---|---|---|---|
Action | a..20 | M | The parameter Action defines the type of transaction: Credit |
an32 | M | ID assigned by Paygate for this transaction | |
a..50 | M | OK (URLSuccess) or FAILED (URLFailure) | |
an8 | M | Error code according to Paygate Response Codes (A4 Error codes) |
Description of result parameters within the record for Batch files