Swish Sweden Instant Payment API
Swish Sweden instant payment REST API for Swedish merchants to accept mobile-to-merchant QR and deeplink payments from Sweden's dominant instant payment platform backed by major Swedish banks (Swedbank, SEB, Handelsbanken, Nordea, Länsförsäkringar) with 8+ million users for e-commerce, in-store, and in-app merchant payment integration. Enables AI agents to manage Swish payment request creation for Sweden instant payment checkout automation, handle QR code generation for Sweden in-store merchant payment automation, access payment deeplink for Sweden mobile app checkout automation, retrieve payment status and confirmation for Sweden transaction automation, manage refund processing for Sweden order management automation, handle callback notification for Sweden payment webhook automation, access transaction reporting for Sweden payment analytics automation, retrieve Swish settlement for Sweden payment reconciliation automation, manage Swish for e-commerce payment for Sweden digital checkout automation, and integrate Swish with Swedish e-commerce, retail, and event ticket platforms for end-to-end Sweden payment automation.
Score Breakdown
⚙ Agent Friendliness
🔒 Security
Swedish payments. FI regulated. mTLS certificate. SE. Instant payment data.
⚡ Reliability
Best When
A Swedish merchant or developer wanting AI agents to automate Swish instant payment acceptance, QR code generation, and payment confirmation for Sweden's dominant mobile payment platform.
Avoid When
SWISH CERTIFICATE AUTHENTICATION: Swish API requires merchant SSL certificate (not API key) for authentication — certificates are obtained through merchant's Swedish bank; automated integration requires certificate management; automated API key authentication creates unauthorized. SWEDISH MOBILE NUMBER REQUIRED FOR CONSUMER: Swish consumer payments require Swedish mobile phone number (+46); automated payment requires customer's Swedish mobile number; automated payment without Swedish number creates consumer lookup failure. CALLBACK MUST BE PUBLIC HTTPS WITH VALID CERT: Swish sends callbacks to merchant-provided HTTPS URL with valid SSL certificate; automated callback endpoint must have valid public SSL certificate; automated self-signed certificate callback URL creates Swish TLS verification failure. AMOUNT IN ÖRES (SWEDISH CENTS): Swish amounts are in Swedish öre (1 SEK = 100 öre); automated amount must use öre denomination; automated SEK amount creates 100x underpayment.
Use Cases
- • Accepting Swish instant payments from Sweden e-commerce checkout agents
- • Generating QR codes for Sweden in-store Swish from merchant POS agents
- • Processing Swish deeplinks from Sweden mobile app payment agents
- • Confirming Swish payment callbacks from Sweden transaction agents
Not For
- • Non-Swedish payments (Swish is Sweden-only with Swedish bank account required)
- • International card processing (use Klarna or Stripe for Sweden card/European payments)
- • B2B invoice payments (Swish is consumer mobile-to-merchant focused)
Interface
Authentication
Swish uses mutual TLS certificate authentication (mTLS) — merchants obtain certificate via Swedish bank. REST API with JSON. Stockholm, Sweden HQ. Founded 2012 by Getswish AB (Swedbank, SEB, Handelsbanken, Nordea, Länsförsäkringar JV). 8M+ users (70%+ of Swedish population). Products: M-Commerce (e-commerce), QR, deeplink, POS, E-commerce Swish. SDKs: Node.js, PHP, Python, Java, .NET, Ruby. PCI DSS. Finansinspektionen regulated. Sweden's dominant payment system.
Pricing
Stockholm SE. Bank consortium owned. Per-transaction fees in SEK via bank agreement. Certificate from bank. FI regulated.
Agent Metadata
Known Gotchas
- ⚠ MTLS CERTIFICATE AUTHENTICATION NOT API KEY: Swish uses mutual TLS certificate authentication — automated integration requires certificate private key and certificate from Swedish bank; automated API key approach is incompatible; automated certificate management must handle certificate rotation before expiry
- ⚠ PAYMENT REQUEST ID IS UUID FORMAT: Swish paymentRequestToken must be UUID format with uppercase letters; automated payment ID must use UUID; automated lowercase UUID or non-UUID format creates validation error
- ⚠ CALLBACK REQUIRES VALID PUBLIC SSL CERTIFICATE: Swish callback delivery requires merchant endpoint to have valid CA-signed SSL certificate; automated development with self-signed certificate creates callback delivery failure; automated production deployment must use valid SSL cert from trusted CA
- ⚠ SWEDISH MOBILE NUMBER FORMAT REQUIRED: Swish consumer lookup requires Swedish mobile number in +467XXXXXXXX format; automated payment must format phone number correctly; automated missing country code or wrong format creates phone number validation failure
- ⚠ AMOUNT IN ÖRES NOT SEK: Swish amounts are in Swedish öre (1 SEK = 100 öre); automated checkout amount conversion must multiply SEK by 100; automated SEK passthrough as amount creates 100x underpayment accepted by Swish without error
Alternatives
Full Evaluation Report
Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for Swish Sweden Instant Payment API.
AI-powered analysis · PDF + markdown · Delivered within 30 minutes
Package Brief
Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.
Delivered within 10 minutes
Score Monitoring
Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.
Continuous monitoring
Scores are editorial opinions as of 2026-03-07.