Skrill: wallet and cards

1) What is Skrill and when to choose it

Skrill is a stored-value electronic wallet from the Paysafe group with wide coverage for digital goods and iGaming. The user keeps a balance, makes a P2P, pays merchants, and can also use a Skrill card (virtual/plastic on Mastercard rails - availability varies by country). For the merchant, Skrill gives high conversion due to App2App/Hosted checkout, low fraud (SCA, device binding, risk scoring) and loyal audience (VIP statuses).

• Digital content, games, subscriptions, gambling (in permitted jurisdictions/by contract).
• Cross-border payment when quick wallet returns/player payouts are needed.
• Like a "second wallet" in a mix of methods next to cards and A2A.

2) Ecosystem and roles

Skrill (scheme/wallet issuer): AUP rules, limits, KYC/AML, risk scoring, wallet book.
PSP/Acquirer (including Paysafe): merchant onboarding, tariffs, Hosted/Widget/API, reports and calculations.
Merchant: initiates payment/return/payment, processes statuses, conducts reconciliation.
Payer: logs into the Skrill/App2App, confirms the SCA, manages the balance/card.

3) Products and scenarios

3. 1 Pay-in (wallet)

Hosted/Redirect (recommended): on the checkout → redirect to Skrill → login/SCA → confirmation → return to merchant.
App2App/Deeplink: the Skrill application opens from the mobile; seamless return to the till.
Embedded/Widget: the widget is embedded in your page (carefully for security requirements).

3. 2 Top-up sources in the wallet (at the user)

Maps (3DS2),

A2A/open-banking (country specific)

eCash/vouchers (local),

P2P inside Skrill.
Recruitment depends on risk/geo and KYC level.

3. 3 Payouts / Withdraw

Payments to the Skrill wallet (disbursements/affiliate payouts).
Output by the user: to the bank (SCT/ACH/local), to the card or cash/agents - where available.

3. 4 P2P/Request-to-Pay

Transfers between wallets by email/ID; R2P scenarios (request for payment) are possible.

3. 5 Skrill card (Mastercard)

Virtual/plastic card, offline/online payments; the write-off comes from the wallet balance.
3DS/SCA for online, PIN/NFC for POS; cash out at ATMs with support.

4) Statuses, Settlements and Finance

4. 1 Standard status model

`created → pending → success | failed | canceled | expired`

Optional: 'authorized → captured '(if separate authorization is used).

4. 2 Settlement and reports

Merchant Fincredit: usually T + 1/T + 2 business days per PSP registers.
Online success is not equal to accounting: keep daily auto-recon and periodic full-recon.

4. 3 Returns and disputes

Refund - a separate credit transaction (full/partial) back to the wallet/source.
Chargeback: for payments from the wallet balance - as a rule, there is no classic card chargeback; if the payment went on card rails (COF/card in Skrill), a card procedure on the part of the issuer is possible.
ODR/complaints: per Skrill/PSP procedures; store service logs.

5) Limits, KYC and risk policy

Per-transaction, per-day/24h, sometimes weekly/monthly; lowering thresholds for new recipients/merchants.
KYC user levels (basic/extended/VIP) define limits on top-up/expense/output.
Velocity/device/geo-rules and terror with restrictions.
For iGaming - separate license/geo-filter/age requirements.

6) Economy and tariffs

Commissions for merchant are usually lower than CNP cards; depends on geography/turnover/category (MCC).
Additional costs: Hosted/SDK, support for'pending/expired', ODR/support, recon, deductions/reserves (for risk).
Skrill VIP programs stimulate wallet activity → increase conversion and LTV in some markets.

7) UX patterns affecting conversion

Mobile-first: offer App2App, on the desktop - clear Redirect.

Timers for waiting for confirmation ('pending'), button "repeat."

Clear errors: wallet/method limit, SCA failure, timeout; immediately offer alternatives (maps/A2A).
Receipt: amount, currency, 'transactionId', channel (App2App/Hosted), UTR/fin ref from registries.

8) Merchant integration

8. 1 Options

1. Hosted/Redirect - fast startup and minimal PCI/PII footprint.
2. Server-to-Server + App2App/Hosted PIN-entry - your UX, status control; comply with safety requirements.
3. Pay-by-Link/Invoice - reference/deferred payments, collection.

8. 2 Backend minimum

API: `createPayment`, `authorize/capture` (если нужно), `refund`, `queryStatus`, `webhook`, `reconcile`.
Idempotence ('orderId' + key), exponential repetitions, dedup of incoming web hooks.
Webhooks: signature/NMAS, timestamps, replay protection.
Recon: auto-reconciliation on daily registers + periodic full-recon; keep the bank reference/UTR.
Observability: conversion, 'pending→success/expired', latency to settlement/refund, SCA/limit errors.

8. 3 PCI/security

In the Hosted scenario, the PCI load is minimal (you do not process PAN/secrets).
Secrets/keys in the vault, IP-allowlist to your callback endpoints, strict redirect-URIs.

9) Antifraud and behavioral signals

Device and behavior profiling, geo-anomalies, repeated unsuccessful attempts.
Restrictions on new recipients/payouts, cooling-off, step-up authentication.
For digital goods: delayed issuance until settlement/passage of risk checks, protection against bonus abuse.

10) Features for iGaming and "sensitive" verticals

Check the validity of geo and licenses, observe age control, Responsible Gaming.
Expect tighter limits, possible hold/reserves, extended monitoring.
Plan alternative rails (A2A/local wallets/vouchers) and smart-routing by risk, geo and player profile.
Payments to players through Skrill are usually comfortable, but observe limits/risk segmentation.

11) Comparison "wallet vs Skrill card"

• Payment from Balance Sheet, SCA in Application/Cabinet.
• Refund - instantly to the wallet; no classic purse balance chargeback.
• Suitable for repeat payments, P2P, quick partial returns.

• Payment on card rails; availability by country.
• Card rules apply (3DS, chargeback on cards is possible).
• Convenient for the user for offline and universal online purchases.

12) KPIs and operational metrics

Approval rate and channel conversion (App2App/Hosted).
Percentage 'pending→expired and average confirmation time.
Refund rate/ODR and time to resolution.
Settlement lag (success → registry → enrollment).
Cost-to-serve (support time per case), VIP share and its contribution to turnover.

13) Output checklist

1. PSP/Skrill Contract - Rates, SLAs, Geo/Verticals, Returns/Payback Policy.
2. Integration selection: Hosted/App2App; implement 'createPayment', error/limit/retry screens.
3. Connect webhooks (signature/NMAS), idempotency and retrai, event dedup.
4. Set up daily recon + full-recon; Store UTR/Fin references, alerts by desynchronization.
5. Enable partial refunds, ODR routines; deferred issuance for risk goods.
6. Dashboards SLA: conversion, 'pending', settlement lag, returns; anomaly/geo alerts.
7. E2E tests: mobile App2App, desktop redirect, timeouts/retries, partial returns, provider degradation.

Landmark card

Statuses: 'created/pending/success/failed/canceled/expired' (+ 'authorize/capture' where necessary).
Settlement: more often T + 1/T + 2 by registers.
Chargeback: for wallet balance - usually not; for a kart rail - there is.
Limits/LCC: country and level specific; keep in the config.
Recurrence: first payment → mandate (SEPA/Open-Banking/wallet-mandate) or COF at the card.

Summary

Skrill is a strong wallet for digital goods and iGaming with good conversion and mature operating system. Integrate through Hosted/App2App, build around webhooks + idempotency + recon, keep limits/LCC/errors in config and monitor 'pending→success/expired'. For high-risk segments - use alternative rails and smart-routing, and for returns - rely on partial refunds and high-quality transaction logs.