Frame the case
Register terminal, operator, amount, currency, transaction and receipt edition.
Workflow blueprint
Credit card point of sale systems should distinguish an authorisation response from settlement
A page-specific review aid, not a universal product or compliance claim.
Use the card-tender evidence card to keep terminal identity, authorisation response, receipt, reversal, refund question and close connected for a Mauritius evidence review.
TL;DR — Use the card-tender evidence card to keep terminal identity, authorisation response, receipt, reversal, refund question and close connected for a Mauritius evidence review.
Trace the evidence
Relate authorisation, timeout, retry, duplicate, reversal and support message.
Review the exception
Keep refund request, customer notice, settlement and close evidence separate.
Assign the next owner
Assign acquirer, payment, tax, security, privacy and reconciliation owners.
Page-specific decision aid
Card-tender evidence card
A terminal, operator, amount, authorisation response, receipt, reversal, refund request and close owner.
- ✓Authorisation is not settlement
- ✓Reversals retain their response
- ✓Receipt is not a bank statement
Scope first
What Codeblix would confirm before implementation
This page is an operational blueprint. The final workflow, screens, permissions and integrations depend on your current process and agreed implementation scope.
- ✓Terminal and transaction identity
- ✓Amount and response source
- ✓Reversal or refund history
- ✓Payment reviewer
Relevant Codeblix foundations
Review the existing product areas that support the proposed workflow.
Use the related planning tools
Run the operational calculation, save the result in the URL and share it with your team.
Map this workflow to your operation
Tell Codeblix how work moves today. We will confirm the practical scope before proposing an implementation.
Discuss your workflow