Quick answer

An MDB payment integration review should identify the exact controller, terminal, harness, mounting, account and network arrangement, then test the customer journey and its exceptions. Use the checklist to approve a specific device combination, with the installation photos and transaction results kept together.

Use this payment checklist when comparing snack and drink vending machines or the separately scoped controller and terminal arrangements for AI vending machines.

Payment integration crosses several responsibilities. The machine supplier may prepare an interface, the provider may control terminal setup and the operator may own the merchant account and site connection. A useful checklist makes those boundaries visible. It also gives buyers and distributors a repeatable way to record what was tested when hardware, settings or ownership change.

MDB payment integration: prepare the device combination

Step 1: identify both ends of the interface

Record the machine controller and the intended payment device, including model identification and relevant revisions. Ask the responsible supplier and provider to confirm the interface and power requirements for that combination. Confirm the controller firmware, device revision, MDB harness and power requirements for the combination being installed.

Identify whether the project is a new build or a change to existing equipment. For an existing installation, retain the current wiring, configuration and fault information needed for review. Use the equipment instructions and appropriately qualified assistance for disconnection, wiring changes and installation work. Attach the approved wiring and mounting instructions to the work order before the installer begins.

Step 2: confirm the physical installation

Review the harness, connectors, mounting position, enclosure access and the route of any required cables. Ask which components are included, which are supplied by the buyer and which require provider approval. Keep mounting photos, harness references and device identities in the equipment file for future replacement checks.

Check the customer-facing position and operator service access. A terminal that fits a panel opening can still create a poor interaction or interfere with another task. Have the site team review access requirements for the intended position. Artwork and instructions should match the actual payment sequence without obstructing hardware or maintenance access.

Step 3: define account and connection responsibilities

Name the business that accepts payment and the party authorized to manage the provider account. Confirm onboarding and support requirements with that provider. Obtain the provider's confirmation of account activation and the approved device arrangement before the acceptance test.

Describe the connection available at the intended position and the process for investigating interruptions. For a US project, use the related cashless payment planning guide to organize the local provider discussion. Ask the provider to confirm the destination and account setup for the exact equipment being purchased.

Step 4: agree what successful integration means

Write the expected customer sequence and the evidence used to review it. Identify product selection, authorization or other provider-defined payment states, delivery, collection and transaction recording. Ask the supplier and provider to explain how their records can be related during an exception.

Use precise language for the outcome. Label payment requests, authorizations and completed sales using the provider's terms so staff can identify each state correctly. Define how the operator determines whether a remedy is needed and which party can authorize it. The acceptance criteria should describe the actual selected arrangement rather than a generic expectation of automatic refund behavior.

Use a transaction test matrix

ScenarioWhat to observeEvidence to compare
Successful purchaseSelection, payment, delivery and collectionMachine event and provider record
Declined paymentCustomer message and sale outcomeProvider status and machine response
CancellationAllowed customer action and resulting stateRelevant transaction references
Unavailable productSelection handling and customer instructionsStock or availability information
Delivery exceptionCustomer outcome and support procedureFault and payment records
Interrupted connectionBehavior and recovery procedureConnection, device and transaction information

Select scenarios appropriate to the configuration and perform them through the agreed test process. Ask the provider to define the cancellation and offline behavior included in the selected setup. Record observations and corrective actions, and repeat affected tests after a material change rather than keeping an obsolete acceptance result.

Connect transaction references with fleet reports

A provider record can answer a different question from a stock or machine-status record. Identify which information is available in each system and who can access it. Avoid assuming that an interface automatically includes remote inventory, a dashboard or an export function.

Review AI and smart vending configurations if connected operations are part of the brief. Confirm data ownership, account permissions, subscriptions and the specific event detail required. The operator should be able to explain what action a record supports, such as investigating an exception or deciding whether a site visit is needed.

Test with the intended merchandise

Include product delivery and collection in the payment acceptance test. Use representative packages and the proposed loading arrangement so delivery and collection are part of the review. Complete the test with stocked merchandise so the customer receives the selected item and staff can compare the delivery event with the payment result.

For mixed products, compare snack and drink equipment and the combo configuration against the same test brief. Ask which hardware and options the order actually includes. Mark the selected controller, delivery layout and payment options on the approved order sheet.

Common integration errors: turn them into sign-offs

  • Order a named terminal and harness before approving the mounting drawing.
  • Confirm the merchant-account owner and provider contact before testing.
  • Save a result for successful, declined, canceled and failed-delivery scenarios.
  • Review the device sheet when a controller, terminal or setting changes.

For an acceptance session, give one person the customer role and another the operator view. Complete a purchase, identify its machine event and find the corresponding provider reference. Repeat the relevant exception tests and write down the recovery action and authorized contact. This produces a handoff checklist that staff can actually use.

Assemble the buyer acceptance packet

Provide a controller and terminal inventory, the proposed connection and mounting arrangement, site information, account ownership and a merchandise list. Include the test matrix, responsibilities and the evidence expected from each party. Identify unresolved dependencies before a purchasing milestone requires a decision.

After testing, retain the accepted combination, observed outcomes, corrective actions and support contacts. Record how a replacement device or ownership change will be reviewed. This packet makes integration repeatable for distributors and gives operators a clear starting point for diagnosing future exceptions without guessing what was originally supplied.

Frequently asked questions

Is MDB compatibility enough to accept a payment installation?

No. Confirm the particular hardware, interface, physical installation, account and connection arrangement, then test the relevant transactions. Keep the supplier, provider and operator responsibilities beside the tested hardware and connection details.

What information is needed for a retrofit review?

Identify the existing controller, wiring arrangement, relevant settings and intended payment device. Include site access and connection information and ask the responsible parties which changes are permitted. Retain the original equipment file and use appropriate technical assistance rather than improvising a replacement solely from connector appearance.

Should failed delivery be part of payment testing?

Yes, include relevant exception scenarios in the agreed acceptance plan. The operator needs to understand the customer outcome, available machine and provider records and the remedy procedure. Agree the available refund or reversal procedure with the selected provider and test the relevant scenario.

Does MDB include remote inventory reporting?

Confirm payment services and fleet-management services as separate lines in the selected setup. Confirm the selected controller, software and connection scope, along with account ownership and recurring arrangements. Payment records, stock information and fault reporting may serve different purposes and require separate review.

When should integration tests be repeated?

Review the test plan when a material device, controller, wiring, setting, provider or account arrangement changes. Ask the responsible parties which scenarios are affected. Keep the revised configuration and results together so staff can identify the currently approved setup and its latest transaction results.

Prepare a configuration review

Send the terminal datasheet and destination country before the machine configuration is frozen.

Request project guidance