What does the customer understand?
Approve the service, amount, currency presentation, timing, cancellation, receipt, refund, language, and help route before connecting a provider.
Commerce board
Put every version of “paid” on the same wall.
The customer interface, payment provider, fulfilment system, invoice, support record, settlement report, and accounting process can disagree. A Uruguay-facing build should expose those differences and assign a person to resolve them.
What did the provider report?
Model authentication, pending, decline, timeout, duplicate request, completion, refund, dispute, and settlement with traceable identifiers.
What may the organisation do next?
Define when access or fulfilment begins, who handles exceptions, how records reconcile, and what evidence customer support can see.
Who owns the commercial conclusion?
The organisation and its qualified advisers confirm contract currency, UYU or USD presentation, invoice treatment, VAT, withholding, territorial, accounting, and customer-classification questions.
Current authority starting points
Frame the question before opening the link.
The Central Bank of Uruguay offers official financial-system context. The Dirección General Impositiva is a starting point for current tax material. Neither page confirms a specific provider route or result for a particular transaction.
Workshop failure cards
- Customer retries during a delayed response
- Amount or currency differs across records
- Refund exists at the provider but not in support
- Receipt language is not approved
- Credential expires before reconciliation
- The commercial owner changes the model
Bring one order that required manual explanation.
Remove personal data, preserve record identifiers and state transitions, and show where the organisation lost a shared view.