![]() The Swish app is activated automatically and preloaded with payment information. The consumer chooses to pay with Swish from the merchant’s app or website. ![]() In this case the consumer does need to open the Swish-app. The consumer initiates the payment on the merchant’s app using a mobile device. The consumer signs the payment with Mobile BankID.Ī payment confirmation is shown in the Swish app. The consumer opens the Swish app, which is preloaded with payment information. In this case the consumer needs to open the Swish-app. The consumer initiates the payment on the merchant’s website using a computer or mobile device. It is always the consumer that initiates a payment, and there are two ways to do it Swish e-commerce or Swish m-commerce. When a certificate reaches its due date, the security solution will notify appointed contact persons if these persons have reported their contact information (this functionality will be developed before first certificate will become invalid). It is possible to issue one or more certificates. Revocation of a specific certificate will not affect other issued certificates. Administrations of certificates include view, order new/download and revoke. An appointed person can administer the merchants’ certificates using the GUI. A merchant appoints up to 5 persons via their bank, who will be able to logon to an administrative GUI connected to the security solution (identified by BankID/BxID on card or Mobile BankID). The security solution is implemented as PKI based TLS client/server certificates, where the certificates are issued upon order by the merchant or someone appointed by the merchant. In order to protect the Swish API and to ensure the identity of the parties, the security solution encrypts the traffic and authenticates the identities of the merchant and Swish server. Information to be published in version 1.0 For a consumer it is the mobile number and for a merchant it is the Swish number. This is the Swish customer that makes the paymentĪ unique identifier for a Swish customer. This is the Swish customer that receives the payment This is any customer to Swish, either a consumer (person) or a merchant. Swish payments initiated by the consumer in a browser in equipment other than the mobile device that hosts the Swish app. Swish payments from a mobile device made either through an app or via a mobile browser on the same mobile device. The service can be offered by the banks under a different product name than Swish handel. All of them are reachable for the merchants through Swish API. Swish handel consist of two different payment solutions Swish m-commerce and Swish e-commerce, a security solution and a function for refunds. ![]() ![]() The service is aimed primarily for m- and ecommerce stores, via apps and browsers. Swish handel gives the merchants the possibility to use Swish as a payment method in m- and e-commerce. Merchants sign Swish agreements with their respective bank.Ī consumer is a private Swish customer that can use the Swish app on a mobile device. The partner will be able to retrieve the security key on behalf of the merchant.Ī merchant is a company, association or organisation which receives payments via Swish. Banks have agreements with the merchants who in turn may have an agreement with a partner. 29Īdded error codes in 11.1.3 Added error codes in 11.2.1 Updated and changed 5.1Ī partner is a company, working with technical integrations, app development, platform development and/or payment services that may help and facilitate merchant integration and operation for Swish. 12 5.1ĭETECTING IF SWISH APP IS INSTALLED ON THE DEVICE. Integration Guide Swish API version 0.9.1 ![]()
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |