Swish gambling merchant payment integration Sweden: requests and compliance checks
Understand the documented Swish merchant payment request and related APIs, alongside the separate payment-provider and account-matching checks identified by the Swedish Gambling Authority.
Play nowSwish gambling merchant payment integration Sweden is a topic with two distinct parts: the payment functions documented by Swish and the checks that a Swedish gambling licensee must perform separately. Swish documents merchant payment requests that appear in the customer’s Swish app, as well as APIs for refunds and payouts to customers connected to Swish.
Those documented payment functions do not replace the licensee’s separate obligations. The Swedish Gambling Authority says that a licensee may receive deposits into a player account only from a payment service provider under the payment-services law. It also says the licensee must be able to ensure that the payment account holder matches the player account holder when funds are deposited.
What the documented merchant payment request does
Swish documents merchant payment requests that appear in the customer’s Swish app. This identifies the customer-facing destination of the request without establishing whether a particular gambling operator, merchant account or commercial arrangement supports Swish.
For integration planning, teams can treat the merchant payment request as the documented payment function. Operator acceptance, availability and suitability should not be inferred from that function alone because those points are not established by the supplied evidence.
- A merchant can initiate the documented merchant payment request.
- The payment request appears in the customer’s Swish app.
- The supplied evidence does not establish acceptance by any named gambling operator.
Refund and payout functions are documented separately
Swish also documents APIs for refunds and payouts to customers connected to Swish. These functions should be considered separately from the merchant payment request because the documentation identifies them as distinct API capabilities.
The supplied facts do not establish fees, limits, processing times, settlement arrangements or gambling-specific availability for these APIs. Those details therefore should not be assumed when defining a merchant integration.
- Swish documents an API for refunds.
- Swish documents an API for payouts to customers connected to Swish.
- No fee, speed, limit or settlement claim is established by the supplied evidence.
The payment-service-provider requirement is a separate check
The Swedish Gambling Authority says that a licensee may receive player-account deposits only from a payment service provider under the payment-services law. This regulator statement concerns how a licensee receives deposits; it is separate from the technical description of a Swish merchant payment request.
A payment team can document the API function and the regulatory check as separate workstreams. The supplied evidence does not establish that using a documented Swish API, by itself, satisfies the regulator’s requirement in a particular implementation.
- Identify the documented payment function being considered.
- Separately assess the payment service provider involved in receiving player-account deposits.
- Do not treat API documentation as evidence that a particular implementation satisfies the regulator’s requirement.
Account-holder matching remains the licensee’s responsibility
The Swedish Gambling Authority says a licensee must be able to ensure that the payment account holder matches the player account holder when funds are deposited. This is a distinct control question and is not established merely by the presence of a payment request in the customer’s Swish app.
The supplied evidence does not describe the technical process a licensee should use to perform this matching. An implementation description should therefore distinguish between the documented payment interaction and the licensee’s separately required ability to ensure that the two account holders match.
- The relevant comparison is between the payment account holder and the player account holder.
- The check applies when funds are deposited.
- The supplied facts do not specify a technical matching method.
Keep the integration scope evidence-based
A concise integration scope can record the merchant payment request, refund API and payout API as documented Swish functions. It can then record the payment-service-provider requirement and account-holder matching as separate matters identified by the Swedish Gambling Authority.
This separation avoids implying that documented API functionality proves gambling acceptance or regulatory compliance. The supplied evidence supports the existence of the listed Swish functions and the two regulator statements, but it does not establish operator availability, commercial terms or a complete compliance process.
- Document the payment request, refund and payout functions without adding unsupported commercial terms.
- Record the regulator’s deposit and account-holder requirements separately.
- Do not infer acceptance by a casino or other gambling operator.
Frequently asked questions
What can the Swish merchant API request?
Swish documents a merchant payment request that appears in the customer’s Swish app. The supplied evidence does not establish acceptance by any particular gambling operator or provide fees, limits or processing times.
What other customer payment functions does Swish document?
Swish documents APIs for refunds and payouts to customers connected to Swish. The supplied facts do not establish gambling-specific availability or commercial terms for those functions.
What must a Swedish gambling licensee check separately?
The Swedish Gambling Authority says a licensee may receive player-account deposits only from a payment service provider under the payment-services law. It also says the licensee must be able to ensure that the payment account holder matches the player account holder when funds are deposited.
Primary sources
- Swish developer guidesChecked 2026-09-22
- Swedish Gambling Authority: operator questions and answersChecked 2026-09-22
- Swedish Gambling Authority: betting player-account checksChecked 2026-09-22
Last reviewed:
Continue to the sponsored casino route
This link opens a sponsored casino route. Review the destination independently; no payment-method acceptance, availability, legality or outcome is promised.
Play now