Neosurf: cash vouchers

1) What is Neosurf and when to choose it

Neosurf is a prepaid voucher payment method: the user buys a voucher for cash/card from offline partners (kiosks, supermarkets, gas stations) or replenishes myNeosurf's balance and then pays online by entering the voucher's PIN or logging in to the wallet. Funds are debited instantly, there is no risk of chargeback, as in cards; returns are issued as separate credit transactions according to provider/PSP rules.

Where works well

Digital goods, games, subscriptions with a low check.
Audiences with low card penetration/confidence in cash.
Markets with a developed retail chain selling vouchers.

2) Ecosystem and roles

Provider/scheme: voucher issue, KYC/KYB rules, anti-fraud, myNeosurf wallet.
Retail chain: sale of vouchers/replenishment of wallets, issuance of a check with a PIN.
PSP/acquirer: merchant connection, hosted cash desk/SDK/API, statuses, reports and calculations.
Merchant: initiates payment, processes statuses and returns, conducts reconciliation.
Payer: Enters a PIN or enters myNeosurf and confirms the charge.

3) Products and scenarios

Neosurf Voucher (PIN): payment by one or more vouchers; partial write-offs and voucher combinations (within limits) are supported.
myNeosurf (wallet): payment from the balance; convenient for repeat purchases and returns.
Invoice/Rau-by-Link: payment link from PSP with PIN entry/wallet entry on the hosted page.

4) Payment flows

4. 1 Hosted/Redirect (recommended)

1. Checkout → select Neosurf.
2. Redirect to the PSP/provider's hosted page → enter a PIN or log in to myNeosurf → confirm.
3. Return to merchant with'status' (success/failed/canceled/pending) and'paymentId '.
4. The final loan is reflected in the daily registers (settlement).

4. 2 Embedded/Widget

Built-in PIN/myNeosurf widget at the checkout. Requires compliance with UI/security and provider policy.

4. 3 Server-to-Server

The merchant's backend initiates the payment and polls the status; The PIN is always entered on the provider/widget side so as not to store sensitive data.

5) Limits, KYC and behavior

• Per-transaction, daily/weekly limits.
• Limit the number of vouchers per payment.
• Geo-restrictions (voucher country vs merchant/wallet country).
• For new merchants/categories - reduced thresholds, step-up checks.

6) Statuses, settlements and returns

Online statuses: 'success', 'pending', 'failed', 'cancelled', 'expired'.
Settlement: credit according to PSP/provider reports (usually T + 1/T + 2 working days, contractually).
Chargeback is missing.
Refunds: separate credit transaction (in myNeosurf or through an agreed channel); partial refunds are supported.
Partial charge-off: Balance remains on PIN/wallet (depends on setting/region).

7) Economy and tariffs

Tariffs, as a rule, below the CNP-card MDR, vary by geo/volume/category (games, digital services, etc.).
Additional costs: hosted/SDK, support and ODR, processing 'pending/expired', recon.

8) UX box office patterns

Where to buy a voucher: Card/point-of-sale searches boost beginner conversion.
PIN combination: convenient UI for adding multiple vouchers + showing balance.

Clear errors: "incorrect/already used PIN," "limit exceeded," "region not supported."

Receipt: amount, time, 'paymentId', method (PIN/myNeosurf); 'refundId 'to return.
Localization: currency/language/legal texts of the client's country.

9) Compliance and safety

PIN/wallet authentication and verification is on the provider's side (SCA/behavioral scoring).
PII minimization: do not process your PIN; use hosted/widget.
Webhooks: HMAC/nonce, replay protection, event dedup, audit.
KYC/AML/GDPR: age and limit requirements for prepaid funds; sanctions/geo-restrictions.

10) Reconciliation and reporting

Log: 'paymentId', 'orderId', method (PIN/myNeosurf), currency, amount, status, timestamps, bank/financial reference (UTR) from PSP registries.
Daily: auto-recon cash events with financial registers (credits/returns/corrections).

Alerts: "success without an entry in the register," "double write-off," "long hanging pending."

11) Merchant integration

Options

1. Hosted/Embedded from PSP - fast start and security compliance.
2. Server-to-Server + Hosted PIN - status control without processing your PIN.
3. Pay-by-Link/Invoice - for deferred payments and support.

• API: `createPayment`, `refund`, `queryStatus`, `webhook`, `reconcile`.
• Idempotency ('orderId' + key), exponential retrays, DLQ.
• Catalogs: countries/currencies, limits/CCL levels, error codes, SLA metrics.

12) Subscriptions and re-charges

• use myNeosurf as a source of funds (if allowed),
• or SEPA/Open Banking → for future debits.
• Show the user the ticket management screen (limit/frequency/notifications).

13) Antifraud and risk policy

Signals: geo mismatch (IP/voucher/merchant), frequent PIN errors, repeated attempts, account communication through the same PIN.
Mitigition: limit on the number of PINs per session/day, cooling-off, captcha/step-up, soft failures with explanation.

14) High-risk verticals (including iGaming)

Availability, thresholds, and reporting vary by country and provider/PSP policy.
Expect reduced limits, increased transaction monitoring, and verification requirements.
Keep alternative rails (other vouchers, A2A, cards) and smart-routing.

15) Neosurf Gateway architecture

Cash/billing API layer (REST/GraphQL).
Event queues: statuses → billing/CRM/analytics/support.
Security: vault of secrets, IP-allowlist, strict redirect-URI validation, anti-replay tokens.
Observability: conversion (PIN vs myNeosurf), 'pending→success/expired', average latency, share of partial/combined write-offs, return metrics.

16) Output checklist

1. Connect the channel at the PSP and enable Hosted PIN/myNeosurf.
2. Implement 'createPayment' + web hooks (HMAC), idempotency and repetitions.
3. Include partial refunds, voucher combination scripts, and understandable errors.
4. Set up daily auto-recon + periodic full-recon; keep fin references/UTR.
5. Dashboards SLA and alerts to suspended 'pending', high proportion of 'failed', geo anomalies.
6. E2E tests by country/currency: multiple PINs, partial returns, expired PINs/limits.

Landmark card

Statuses: 'success/pending/failed/canceled/expired'.
Settlement: usually T + 1/T + 2 across registries.
Chargeback: none; refund - a separate credit transaction (in parts allowed).
PIN combination: allowed within limits.
Recurrence: via myNeosurf or alternative mandate (after the first payment).

Resume Summary

Choose Neosurf for cash and micropayments: hosted PIN/myNeosurf → fast and secure.
Build the process around webhooks + recon, support partial refunds and a combination of vouchers.
Do not "lick" the amounts: keep limit/CCL configs by country and update regularly.
For subscriptions, the first voucher →/myNeosurf ticket with transparent management and notifications.