Wallet Payment Solutions

Follow the money step by step. You will trace a wallet payment from tap to settlement and use the terms authorise, capture and settle correctly when talking to a partner.

• Customer authorises; the wallet provider checks funds and identity.
• Merchant is told yes or no; money settles later.
• Fees are taken before settlement.
• Records on both sides must match.
• Trace one payment of 20.00 (in your currency) through five steps on paper: customer taps pay, wallet app sends a token, partner checks it, the bank approves, and the shop receives a confirmation.
• Learn three terms: authorise, capture and settle. Authorise reserves the money, capture claims it, and settle moves it to your account, often one to three working days later.
• Draw the journey from basket to receipt.
• Check which wallets are common among your customers.

Activity. Draw the flow with arrows and time.

Standard to meet. Draw the flow so that it shows each party and time.

Common mistake. Thinking payment is done when the customer taps.

Check yourself. When does money reach you?

Pick on safety and fit, not on price alone. You will score licensed partners on fees, support, tools, payout speed and reporting, and justify your choice with written evidence.

• Licensed and regulated; clear terms.
• Fees: percent, fixed, refund and dispute fees.
• Settlement time; support; local methods.
• Data handling and security.
• Score three licensed partners from 1 to 5 on fee clarity, support response, test tools, payout speed and reporting, and favour the one with the highest total, not the lowest price.
• Ask each partner in writing for their list of fees, their payout schedule and what they do when a payment is disputed, and keep the replies in a folder.
• Keep test keys in a protected place only.
• Write the exact wording for payment failure messages.

Activity. Compare three partners on a table.

Standard to meet. Calculate the fees on three sale sizes.

Common mistake. Picking the lowest percent without the fixed fee.

Check yourself. Which partner is cheaper at your average sale?

Always rehearse without real money. You will run ten rehearsal payments with test keys, including declines and timeouts, and keep secret keys out of any shared place.

• Create a test account; use test credentials supplied.
• Link a simple checkout.
• Use test wallets to simulate success and failure.
• Keep keys private and out of documents.
• Work only with test keys and fake card numbers supplied by the partner, and keep the secret key out of web pages, shared documents and screenshots.
• Run at least ten test payments: five that succeed, three that are declined, and two that time out, and note exactly what the screen shows in each case.
• Check support hours and escalation of the partner.
• Record every refund with a reason.

Activity. Run 10 test payments.

Standard to meet. Record all ten.

Common mistake. Pasting keys into documents.

Check yourself. Where are your keys?

Customers and tax offices need clear proof. You will issue receipts quickly and keep a monthly payment log, so every sale can be proved to a customer or a tax office.

• Receipt: date, seller, items, taxes, total, reference.
• Number receipts in order.
• Send by email or message with consent.
• Keep records for the legal period.
• Send a receipt to every customer within one minute, showing date, items, total, tax if any, a payment reference and a contact for questions.
• Keep a monthly record file with one row per payment and store a copy outside the system; check that the number of rows equals the partner's report each week.
• Check whether tax needs to be shown separately.
• Keep daily and weekly reconciliation notes.

Activity. Design a receipt and send one in test mode.

Standard to meet. Check that the receipt has all fields.

Common mistake. A receipt without a reference.

Check yourself. Does every receipt carry one?

Things go wrong: plan for them. You will write plain messages for four common failures and follow a fixed refund routine, keeping customers informed and trusting.

• Common failures: low funds, timeout, wrong details.
• Say what happened and what to do next.
• Refund rules: when, how long, who pays the fee.
• Avoid double charges.
• Write a plain message for each failure: card declined, timeout, duplicate charge and wrong amount, telling the customer what happened and the next step in under 25 words.
• Set a refund routine: confirm the order, refund to the original method, send a message, and record the date; aim to complete it within two working days.
• Limit who may refund or change prices.
• Alert customers if a payment is pending.

Activity. Test 3 failures and 2 refunds.

Standard to meet. Write messages that are clear and kind.

Common mistake. Refunding without a rule.

Check yourself. What is your refund rule?

Protect the customer and the shop. You will set practical limits, approvals and sign-in protections that make payment fraud harder without slowing honest customers.

• Signs: unusual size, rushed buyers, mismatched details.
• Use partner tools for checks.
• Limit who can refund.
• Never ask for a password or code.
• Add simple limits: block more than five failed attempts per card in an hour, flag orders far above your usual size, and require two people to approve large refunds.
• Keep software and passwords updated, turn on two-step sign-in for every account, and remove access the day a team member leaves.
• Check how chargebacks are handled.
• Set daily limits for new accounts.

Activity. Write a fraud checklist.

Standard to meet. Write a checklist with actions, not just signs.

Common mistake. Letting any helper refund.

Check yourself. Who can refund?

Match every payment to a record. You will match each payout report to your own records and track three monthly measures, so missing money is found within a week.

• Daily match: partner report versus own sales log.
• Investigate any gap.
• Measures: success rate, time to pay, refund rate.
• Chargebacks: reasons and prevention.
• Each week, match the partner's payout report to your own records line by line; any difference above 1.00 (in your currency) or any missing payment goes on a short follow-up list.
• Track three measures monthly: the percentage of payments that succeed, the average time to payout and the refund rate, and compare month to month.
• Test the journey on a slow phone.
• Update the guide when screens change.

Activity. Reconcile 20 transactions and compute measures.

Standard to meet. Complete the reconciliation with no unexplained gap.

Common mistake. Skipping the daily match.

Check yourself. What gaps did you find?

Teach customers and improve. You will write a short customer guide and review a pilot with test users, leaving the shop ready for a safe, approved launch.

• One-page guide with pictures.
• Test it with three real users.
• Fix confusing steps.
• Plan 90 days.
• Write a one-page customer guide with three steps to pay, what to do if it fails and how to ask for a refund, in language a ten-year-old could follow.
• Review the pilot after two weeks with test users, listing what confused them, and only plan real money after a licensed partner and an adviser have approved the setup.
• Keep a list of lessons for each test cycle.
• Plan a pilot with a licensed partner before any real money.

Activity. Write, test and revise the guide.

Standard to meet. Show that three users complete it alone.

Common mistake. A guide that assumes knowledge.

Check yourself. How many users succeeded?

A customer sees two charges after a timeout.

Question: What do you do?

Model answer: Check the partner record, release or refund the duplicate, tell the customer when.

A new account orders 40 phones.

Question: Next step?

Model answer: Hold, verify buyer and address, and use partner fraud tools.

On the slide: L1 Basic · Basics of paying

Notes: Pay with a wallet, check the receipt and explain what happens when a payment fails. Notes: use a small real payment you already make, with a trusted adult if needed. Standard: you can find the receipt, the amount and the reference.

On the slide: L2 Awareness · Awareness

Notes: Describe how a wallet links to a bank or card, what a wallet provider holds, and the main risks (theft, wrong payee, scam). Notes: compare two public wallet explanations in a table. Standard: each risk has a plain action to reduce it.

On the slide: L3 Foundation · Foundation

Notes: Draw the payment journey of one small shop: pay, receipt, failure, refund. Notes: paper map with a time and a person at each step. Standard: no step without an owner and a record.

On the slide: L4 Practitioner · Practitioner

Notes: Run the journey in test mode: five payments, one failure, one refund, and match them to a day sheet. Notes: test mode only; no real money. Standard: the day sheet and the test records agree to the last unit.

On the slide: L5 Specialist · Specialist

Notes: Build and test a wallet payment journey in test mode for one small business, with pay, receipt, failure, refund and reconciliation. Notes: write limits, identity checks and a dispute step. Standard: all paths tested, totals reconcile, disputes have a deadline.

On the slide: L6 Advanced · Advanced

Notes: Lead a rollout across several shops with limits, monitoring and a fraud response. Notes: add a daily exception report and a licence check for the provider. Standard: exceptions are cleared within one day and the provider is licensed for the place.

On the slide: L7 Super expert · Super expert

Notes: Set the wallet onboarding, limits and dispute method and teach the support staff who use it. Notes: re-read the payment and identity rules for the place each year and update the checklist.