A merchant can refund the original purchase currency while the customer's account receives a different converted amount from the initial debit. The explanation depends on the actual programme terms and processing path.
Keep the original and refund currencies visible
The account history should identify the merchant purchase amount, posted account amount and relevant conversion details. The later refund should have the same level of clarity, including any partial amount and applicable charges under the terms. Combining the two into a single net number can conceal the source of a difference. A customer needs to know whether the merchant returned less, the conversion differed or a separate charge applied. The programme's support team needs the same record. Currency conversion at the merchant, including DCC where used, may require additional context from the original receipt rather than an assumption based only on the account display.
Walk through a returned item
Suppose a hypothetical traveller returns goods priced in a local currency after the original purchase has posted. The merchant confirms a refund in that currency. The programme should explain the rule used to convert the return into the supported account balance, including the relevant timing and provider.
The customer should not be told that the difference necessarily represents a merchant error or automatically reflects a programme fee. The actual references and calculation are needed. A clear receipt chain allows support to separate the merchant's returned amount from the account-side treatment and investigate a discrepancy at the stage where it arose.
Separate card refunds from token conversion
A refund credited to a supported spending balance would not automatically reverse the original ALFA funding conversion. The proposed product journey has those as separate events. If the customer later converts or withdraws value through a permitted route, that would follow its own terms and quote. The documentation should avoid suggesting that a returned purchase restores the original number of tokens. That claim would require a specific arrangement absent from the current materials. The distinction matters because otherwise a customer may compare the refund with a token estimate that belongs to another transaction and another point in time.
Prepare support for partial and delayed returns
Testing should include a partial refund, multiple refunds against one order and a refund arriving after a credential change. The account should connect each event to the original purchase while preserving its own date and calculation. The ALFA programme design establishes no guarantee about exchange outcomes or refund timing. A future guide should use approved illustrative figures and explain the relevant rule plainly. The programme's practical duty is to make the completed calculation traceable and correct under its terms, giving customers a dependable explanation when a foreign-currency return does not reproduce the original account amount exactly.
