If a customer says the card code is not working, do not assume they have already used it, and do not promise immediate compensation before verifying. Collect the order number, card type, and error message, check the region and status in your log, then escalate to the supplier or the relevant party. Update the customer with a clear next step and a follow-up timeframe you can commit to, applying the store policy and customer rights according to their case.

The issue could be related to region compatibility, code entry, code status, or supplier fulfillment. There might also be a claim that requires verification. The fair approach remains the same: gather appropriate evidence with minimal required data, followed by a documented decision. Do not ask the customer to send a full secret code in a public comment.

What is the first message to send to the customer?

"We have received your note regarding order [Order Number]. We are reviewing the card type, region, and fulfillment status, and we require a screenshot of the error message after redacting any sensitive information. We will update you with the review status within [a timeframe you can commit to]". State the realistic timeframe for your team; do not copy an "immediate" promise if you are awaiting a response from the supplier.

After that, review the name, value, and region on the product page, followed by the order and payment status, and then the code status or supplier fulfillment. The digital cards log in Salla outlines the status and order details for the codes you manage within the system. If the card is tied to an account in a specific region, refer to its official source; for instance, PlayStation guidelines explain region mismatch issues for some of their codes.

Example of a completed support ticket without exposing the code

The customer wrote: "The code is invalid." The team responded by requesting the order number and a screenshot of the error message via a private channel, with the full name and any sensitive code redacted. The team checked whether the customer selected the correct account country, whether the card delivery appeared in the order, and whether the code status in the Salla log was linked to the correct order. If the information was inconclusive, it was escalated to the supplier with a reference number without posting the code in a comment or a mass message. This is an example workflow, not an actual customer story.

When the supplier’s response arrives, write to the customer explaining what you verified and the decision made in accordance with the applicable policy and rights; do not merely say, "The supplier says the code is valid." If it turns out that the region description on your page was confusing, correct it even if the code was technically valid. Log the issue type and resolution time; the recurrence of a single cause is a signal to update the page or the supplier before overwhelming the support team with similar requests.

Before resending any code, verify the status of the first code and the order status. If the issue is related to how the code was entered, share the official issuing entity's steps rather than requesting the customer’s account password.

A resolution workflow that protects both parties

Do not send a replacement code while leaving the first code valid if both could potentially be used. Do not delay your response until the end of a lengthy investigation. Distinguish between "We received your complaint" and "It has been resolved", and record the date and your decision so you can review recurring causes.

What about refunds and impersonation?

Draft a clear policy suitable for the nature of digital cards and consumer rights, and review current official requirements. The Ministry of Commerce provides an e-commerce compliance checklist and verification guidelines, and you must review how they apply to your business prior to publishing. Do not state "Strictly no refunds" as a blanket rule without legal review, and do not ask the customer to transfer funds to an undisclosed personal account to resolve an issue.

In Cardny's story, the store faced impersonation of its brand and false claims regarding card top-ups. An actionable lesson: make the purchase link and official communication channels prominent, and advise customers not to share their card codes with accounts impersonating the store. Keep order evidence within a secure, access-restricted support workflow.

If you are starting out now, set up your store on Salla with dedicated support and a clear review policy; get started from the digital cards page.

Prompt to summarize a complaint without exposing the code

This is a digital card complaint after removing the name, phone number, and secret code: [ ].
Product details permitted to share: [Region, value, and fulfillment method].
Order status and log as verified: [ ]. Known supplier terms: [ ].
Organize confirmed information, missing questions, and a polite follow-up message to the customer.
Do not accuse the customer, and do not determine the validity of the code or a refund without evidence and applicable policy

This is a digital card complaint after removing the name, phone number, and secret code: [ ].
Product details permitted to share: [Region, value, and fulfillment method].
Order status and log as verified: [ ]. Known supplier terms: [ ].
Organize confirmed information, missing questions, and a polite follow-up message to the customer.
Do not accuse the customer, and do not determine the validity of the code or a refund without evidence and applicable policy

This is a digital card complaint after removing the name, phone number, and secret code: [ ].
Product details permitted to share: [Region, value, and fulfillment method].
Order status and log as verified: [ ]. Known supplier terms: [ ].
Organize confirmed information, missing questions, and a polite follow-up message to the customer.
Do not accuse the customer, and do not determine the validity of the code or a refund without evidence and applicable policy

Complaint handling checklist

• ☐ Linked the complaint to the correct order number and product.

• ☐ Verified the region, payment, and code or supplier status.

• ☐ Requested the minimum necessary evidence from the customer via a private channel.

• ☐ Updated the customer with a realistic review step and timeframe.

• ☐ Logged the cause and resolution, and corrected the product description if it caused the issue.

Frequently Asked Questions

Should I compensate the customer immediately if they claim the code is used?

Handle the matter promptly and respectfully, but verify the code, order, and supplier status in line with a fair policy before making a decision. Delaying without updates damages trust, while compensating without verification may lead to repeated errors.

What if the customer selects a region that does not match their account?

Review whether the region was clear prior to purchase and how the option was displayed, then apply the policy, applicable rights, and code status accordingly. Update the product page if it causes confusion.

How do I warn against store impersonators?

Display the store link and official support channels clearly, and instruct customers to complete payments exclusively through verified paths. Do not publish details that could make it easier to expose their codes or data.

Trust begins with proper setup before the first order: launch your card store on Salla. To register right away, open your account directly.