THE SHORT ANSWER

Do not send the code. A gift card code is a payment method, and sharing it can move value out of your hands. If you already sent it, keep the card, receipt, and message thread, then contact the gift card issuer and any payment company or bank promptly without assuming a refund. Report the account where you can. Reviewing public-profile material can add context but cannot identify who is behind an account, and more searching cannot recover money already sent.

Have a username or photo?

Find public social profile clues with our TraceSeek app.

What the gift card request means

A match who asks for a gift card code is asking you to transfer payment, not to prove trust. Romance scammers may build trust over time and then request money, so treat the request itself as the point to stop the payment conversation. You do not need to decide whether the person is honest before you decline. You also do not need to keep replying to gather more evidence; ending the request is enough. [FTC: What To Know About Romance Scams]

  • Save the message thread before doing anything else
  • Do not type, read aloud, or photograph the code for the match
  • Decline once if you choose to reply, then stop the payment conversation

If you already sent the code

If you already shared a gift card code, act on the payment first. Keep the physical card, the receipt, the code, the time, and the full message thread. Contact the card issuer right away and ask what options exist; a refund is not guaranteed. If money moved through a bank or payment company, contact that company as well and report the account. Further profile searching cannot recover funds, so prioritize the issuer and payment company over looking for more clues. [FTC: What To Know About Romance Scams] [FTC: What To Do if You Were Scammed]

  • Keep the physical card and receipt; do not discard them
  • Contact the issuer and any payment company or bank promptly
  • Report the account through available platform or payment-company channels, if offered

Public-profile clues have a narrow use

If you want context, review only what is already public: the photos and profile text. Research publicly available photos and profiles, and note whether images appear reused. That comparison is a context clue only; it does not confirm identity and should not be used to accuse anyone. Avoid private accounts, location tracking, and contacting third parties. Do not treat an old screenshot, a delayed response, a matching username, or a privacy choice as proof of dishonesty. [FBI: Romance Scams]

  • Compare a public profile photo with other public appearances of the same image
  • Record what you found and what remains unclear
  • Do not treat any public clue as identification or proof of intent

A hypothetical worked example

Imagine a match you have chatted with for two weeks asks you to buy a gift card and send the code, saying they cannot receive payments another way. This example is editorial, not a real case. You do not send the code. You save the thread, note any public reuse of the profile photo as context only, and decline once if you choose. You then stop replying and, if you already paid, contact the issuer and payment company rather than continuing to search. No public-profile check can confirm who is behind the account. [FBI: Romance Scams] [FTC: What To Do if You Were Scammed]

An editorial worksheet for your next step

This table is an editorial worksheet, not a test, a score, or a product feature. It separates what you observed from what that observation cannot show, then suggests a small action. A request, a privacy choice, or an unanswered question is not proof of dishonesty. If a row ends in a stop action, stop the payment conversation and preserve what you have.

Observation you can makeLimit of that observationSuggested next action
Match asks for a gift card codeA request does not prove intent, but you do not need proof to declineDo not send; save the thread and stop
Match avoids meeting and pressures you to leave the dating platformCaution is warranted, but avoidance alone is not proofDo not send money; stop the payment conversation
A public photo appears elsewhereReused imagery is a context clue only, not identificationNote it and stop; do not accuse

Stop, preserve, and report

Stop the payment conversation when a match asks for a code. Do not send money to someone known only online or by phone, and treat pressure to leave the dating platform as a reason for caution. If you already paid, contact the payment company or bank promptly and report the account. Preserve the thread, then decide whether to block and report. A delayed reply or a privacy choice is not a verdict about the person; your priority is protecting the payment, not investigating the profile. [FBI: Romance Scams] [FTC: What To Do if You Were Scammed]

A couple more questions

Should I send a gift card code to prove I trust a match?

No. A code is a payment method, not a trust test. Treat the request as a reason to decline and stop the payment conversation; you do not need to keep replying to gather evidence.

Can public-profile clues prove who sent the request?

No. Public images and profile text may add context, but they are not identity matching and cannot confirm who is behind an account. Do not use them to accuse anyone.

What if I already sent the code?

Keep the card, receipt, code, and messages. Contact the gift card issuer and any payment company or bank promptly without assuming a refund. Report the account where you can, and do not rely on further profile searches to recover funds.

Is reviewing a public profile the same as investigating someone?

No. Review only what is already public, avoid private accounts and location tracking, and do not contact third parties or make public accusations. Public review is context, not proof.

Sources & editorial notes

Official references checked on October 20, 2026. Checklists, comparison tables and example wording are DateClues editorial tools, not official tests or validated risk scores.

General information. No guide or tool can certify a person’s identity, intentions or safety. Read our editorial standards.