A guest says the card “did not work.” That description can cover a reader still waiting for a PIN, a declined payment, a disconnected cable or an approved authorisation followed by no power-bank release. Restarting the cabinet is not the right first response to all four.
Prepare a short classification card for the Swedish venue. Staff record the visible instruction and physical outcome; an authorised operator checks the financial state. Only then should the team decide whether to continue the existing interaction, offer a supported alternative or investigate the equipment.
Define the reader route being investigated
Stripe’s Sweden guidance specifies SEK with a matching Swedish receiving account and reader Location, and lists WisePad 3. The operator buys and registers the eligible local reader. The intended staffed or unattended setting still needs its own suitability confirmation.
CoreCharge’s matched integration places the native Android rental application and Terminal SDK inside the cabinet, using the agreed USB data and reader-power arrangement. No additional merchant phone is needed in the ordinary flow. CoreCharge connects orders, payment outcomes, release, return and pricing; Stripe processes rental funds in the operator’s own account.
Use four categories instead of one failure label
| Observed category | First check | Safe direction |
|---|---|---|
| Reader requests another action | Current tap, insertion or PIN instruction | Let the customer complete the requested step without bypassing it |
| Payment is actually declined | Verified response and any authorised support guidance | Follow the appropriate decline handling; do not assume hardware failure |
| Reader or connection is unavailable | Device connection, application state and physical observations | Report the equipment issue without repeatedly presenting cards |
| Payment approved but no release confirmed | Original payment, rental order and actual cabinet event | Investigate the existing attempt before another charge or release |
The classification is an operating aid, not a claim that every error is automatically routed to the correct team. A bank refusal does not prove that the USB cable failed, and a connection error does not prove that no payment was authorised.
Keep sensitive decline details out of venue conversations
Stripe’s decline-code guidance distinguishes different reasons and next steps. The authorised operator should use the actual response rather than guess the reason from a generic customer message. Some responses require discreet handling; venue staff should not accuse a guest or announce private account information.
A useful response is: “We will check the original attempt before asking you to try again.” If the verified result permits another attempt, follow the agreed flow. A card requiring authentication should not be retried through an improvised route intended to avoid that requirement.
Retry with a known starting point
Confirm whether the first attempt has ended and whether a rental already exists. Do not create repeated independent attempts while the original result is uncertain. If the operator offers another supported payment method, explain it clearly and reconcile the earlier attempt first.
A genuinely declined payment is not automatically a captured charge to refund. Conversely, an approved authorisation with no release needs its own cancellation or recovery investigation. Keep the customer’s visible bank display as context, while using the verified payment record to determine the actual state.
Rehearse the categories before opening
Use Stripe’s Terminal testing tools to exercise supported decline and authentication scenarios in the correct test environment. Observe the cabinet response as well as the reader. Controlled tests should show the staff message, order result and whether any unit physically released.
Review a technical outage separately rather than trying to simulate every failure with repeated live customer payments. Retain redacted evidence and assign an owner for each unresolved outcome.
The PIN and cancellation walkthrough supports the customer interaction. The support-file template makes the resulting investigation traceable.
Explore CoreCharge’s reader station route or request a Sweden payment-attempt walkthrough with your venue support team.
References and project scope
Technical references checked on 17 October 2026. The operating procedures above are planning guidance; hardware, account access and payment settings are confirmed for each deployment.