Payments & Refunds Specialist

About Us:

Platinumlist.net, a pioneering leader in the online event guide and ticketing solution industry, has been revolutionizing the event landscape in the Gulf region since 2009. As the largest ticketing provider in the GCC, we proudly serve an extensive array of events across the United Arab Emirates, Saudi Arabia, Oman, Bahrain, Qatar, and Kuwait from our Dubai-based headquarters.

Your Role:

The Payments & Refunds Specialist owns every customer question about their money — from “did my payment go through?” to “where is my refund?” You investigate the transaction in the payment system, establish exactly what happened, explain it to the customer in plain language, and — where a refund is due — process it and send the proof. The role deliberately combines two sides that are usually split, customer support and accounting, so that payment and refund tickets are never lost in a handover. You work to a written procedure, with a Finance Manager who approves anything above a set limit and to whom you can escalate freely. Accuracy matters more than speed. This is an entry-level, UAE-based role, and full training on our systems and policy is provided.

Key Responsibilities:

1. Checking Payments

• Find a customer's transaction in the payment system and establish exactly what happened — whether the payment succeeded, failed, is still pending, or was only held.
• Tell the difference between a real charge and a temporary hold on a card, and explain that clearly to a customer who believes they have been charged.
• Identify genuine duplicate charges and open a refund where one has occurred.
• Read decline and failure reasons and translate them into something the customer can act on.
• Send the customer confirmation of what you found, with evidence attached.

2. Processing Refunds

• Check each refund request against a checklist: order located, original payment confirmed, amount and currency correct, no refund already issued, eligibility confirmed against policy.
• Process small-value refunds yourself; prepare larger ones for the Finance Manager's approval.
• Issue refunds through the payment system and record the transaction reference against the ticket.
• Follow up and re-issue refunds that fail — expired cards, closed accounts, rejected transfers.
• Attach proof of payment to every completed refund so the customer can see the money was sent.

3. Looking After the Customer

• Own each ticket from the customer's first message through to resolution, across email, chat and messaging.
• Explain our policy in plain language, including when the answer is no — clearly, kindly, and with the reason.
• Give realistic timelines and keep customers updated before they have to chase.
• Handle worry and frustration without matching it: acknowledge the problem, say what you found, give a date, and follow through.
• Record the correct reason code on every ticket and write notes a colleague could pick up without asking you.

4. Keeping the Records Straight

• Match each day's refunds between our ticketing system and the payment system, and report anything that does not match the same day.
• Cross-check your colleague's daily check, and have yours cross-checked.
• Produce a short daily summary of the queue: opened, processed, completed, on hold, and anything running late.
• Gather evidence for chargebacks and disputes to a standard template, and pass it to the Finance Manager.
• Escalate anything the procedure does not cover, rather than deciding it yourself — escalating is expected here, not a failure.

What Success Looks Like:

• The transaction status you report to a customer is correct — always.
• Processing errors (wrong amount, wrong recipient, duplicate refund) — zero.
• Tickets completed within the agreed timeline — 95% or better.
• Completed tickets carrying full proof of payment — 100%.
• First reply to the customer — within 4 working hours.
• Customer satisfaction on your tickets — 4.5 out of 5 or better.
• Customers who had to chase you for an update — under 10%.
• Daily payment check completed and any differences reported — every working day.