If a customer states that a card code is not working, do not assume they have already used it, nor promise immediate compensation prior to verification. Collect the order number, card type, and error message, check the region and status in your logs, and then escalate the issue to the supplier or relevant authority. Update the customer with a clear next step and a follow-up timeframe you can commit to, applying the store's policy and customer rights according to their case.

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

What is the first message you should send to the customer?

"We have received your inquiry regarding order [Order Number]. We are reviewing the card type, its region, and fulfillment status, and we require a screenshot of the error message after masking any sensitive details. We will provide an update on the review status within [a timeframe you can commit to]". State an accurate timeframe for your team; do not replicate an "immediate" promise if you are awaiting a response from the supplier.

Next, verify the name, value, and region on the product page, followed by the order and payment status, and then check the code status or supplier fulfillment. The Digital Cards Log in Salla details the status and order information for codes managed within the platform. If the card is tied to an account in a specific region, consult its official source; for example, 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, masking the full name and any sensitive code. The team verified whether the customer had selected the correct account country, whether card delivery was recorded in the order, and whether the code status in the Salla log matched the correct order. If the details were inconclusive, the issue was escalated to the supplier with a reference number, without sharing the code in a public comment or group message. This serves as a workflow example, not an actual customer case.

Once the supplier responds, explain to the customer what was verified and the resulting decision in accordance with applicable policy and rights; do not settle for merely stating "The supplier says the code is valid." If the region description on your page proved confusing, rectify it even if the code is technically valid. Record the issue type and resolution time; recurring issues indicate a need to adjust the product page or supplier before support is overwhelmed with similar requests.

Before issuing any replacement code, verify the status of the initial code and the order. If the issue relates to how the code was entered, share the official issuing authority's steps instead of requesting the customer's account password.

A resolution workflow that protects both parties

Do not send a replacement code while leaving the initial code active if both could potentially be redeemed. Do not delay your response until an extended investigation concludes. Distinguish between "Complaint received" and "Issue resolved", and document the date and decision to evaluate recurring causes.

What about refunds and impersonation?

Formulate a clear policy tailored to digital cards and consumer rights, and review current regulatory requirements. The Ministry of Commerce outlines e-commerce compliance lists and authentication guidelines, which should be assessed for your business before publishing. Do not implement a blanket "No refunds under any circumstances" rule without legal review, and never direct a customer to transfer funds to an undisclosed personal account to resolve an issue.

In the Cardiny case study, the store encountered brand impersonation alongside claims regarding card redemptions. A practical takeaway: ensure your purchase link and official communication channels are clearly displayed, and warn customers never to share their card codes with accounts impersonating your store. Maintain order records within a secure, access-restricted support system.

If you are just getting started, set up your store on Salla with dedicated support channels and a clear review policy; begin with the digital cards page.

Prompt to summarize a complaint without disclosing the code

This is a digital card complaint with the name, phone number, and secret code redacted: [ ].
Permissible product details to share: [Region, value, and fulfillment method].
Order and log status as verified: [ ]. Known supplier terms: [ ].
Organize confirmed details, missing points, and a polite follow-up message for the customer.
Do not accuse the customer, and do not validate code validity or refunds without evidence and applicable policy

This is a digital card complaint with the name, phone number, and secret code redacted: [ ].
Permissible product details to share: [Region, value, and fulfillment method].
Order and log status as verified: [ ]. Known supplier terms: [ ].
Organize confirmed details, missing points, and a polite follow-up message for the customer.
Do not accuse the customer, and do not validate code validity or refunds without evidence and applicable policy

This is a digital card complaint with the name, phone number, and secret code redacted: [ ].
Permissible product details to share: [Region, value, and fulfillment method].
Order and log status as verified: [ ]. Known supplier terms: [ ].
Organize confirmed details, missing points, and a polite follow-up message for the customer.
Do not accuse the customer, and do not validate code validity or refunds without evidence and applicable policy

Complaint resolution checklist

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

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

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

• ☐ Updated the customer with clear next steps and a realistic review timeframe.

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

Frequently Asked Questions

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

Respond promptly and courteously, but verify the code, order, and supplier status in accordance with a fair policy before deciding. Unexplained delays undermine trust, while compensating without verification can perpetuate errors.

What if the customer selects a region incompatible with their account?

Check whether the region was clearly displayed prior to purchase, how the selection was presented, and then apply relevant policies, consumer rights, and code status. Rectify the product page if it caused ambiguity.

How do I warn customers about store impersonators?

Display your official store URL and support channels prominently, and advise customers to complete payments exclusively through verified paths. Avoid publishing details that could inadvertently expose codes or personal data.

Trust starts with proper setup before the first order: launch your card store on Salla. To get started immediately, open your account today.