Skip to content
English
Go to PAY.NL
  • There are no suggestions because the search field is empty.

Cloud Connect Validation Checklist for Pay.POS

This checklist helps Product Owners, QA teams and implementation partners validate a Pay.POS Inject integration before going live.

Purpose

The goal is to verify that the payment flow, customer experience and transaction information are correctly implemented.

Before you start

Complete the Pay.POS: Getting Started & Choosing the Right Integration checklist before validating the Inject integration.

Minimum requirements

Before starting validation, verify that the following requirements are met.

Integration ownership

The integration must contain sufficient information to identify the application owner.

Required:

☐ stats.object is populated.
☐ The value identifies the application or integration owner.
☐ The value is consistent across transactions.

Why this is important

The stats.object value allows Pay. to identify the responsible integration for monitoring, support and troubleshooting.

  

Terminal connection

Cloud Connect requires a Pay..POS terminal to be connected and available for the POS system.

Verify:

☐ Pay.POS terminal is configured for Cloud Connect.
☐ Terminal is connected to the Pay. platform.
☐ The terminal is visible and available for transaction processing.
☐ The correct terminal is selected for the transaction.

Cloud Connect allows a POS system to initiate payments on a connected PAy..POS terminal through the Pay. platform.

Transaction initiation

Verify that the POS system correctly starts a payment on the selected terminal.

Required:

  • ☐ POS system can initiate a payment.
  • ☐ Correct terminal is selected.
  • ☐ Correct amount is transferred.
  • ☐ Correct currency is transferred.
  • ☐ Transaction reference is included.
  • ☐ Payment appears on the correct PAY.POS terminal.

Payment flow validation

Validate the complete customer payment experience.

Successful payment

  • ☐ Customer can complete a contactless payment.
  • ☐ Customer can use physical payment cards.
  • ☐ Customer can use supported mobile wallets.
  • ☐ Payment result is returned correctly to the POS system.
  • ☐ Transaction status matches the result shown on Pay.POS.

Failed payment

  • ☐ Failed payments return the correct status.
  • ☐ POS system handles failed payments correctly.
  • ☐ Customer receives clear feedback.
  • ☐ Payment can safely be retried.

Cancelled payment

  • ☐ Payment can be cancelled.
  • ☐ Cancellation is correctly processed.
  • ☐ POS system receives the correct status.
  • ☐ No duplicate transaction is created.

Payment status handling

Cloud Connect integrations should correctly monitor the payment status after initiating a transaction.

  • ☐ POS system receives transaction updates.
  • ☐ Final payment status is correctly processed.
  • ☐ Completed transactions are marked as successful.
  • ☐ Failed or cancelled transactions are handled correctly.
  • ☐ Transaction status remains consistent between POS system, Pay..POS and Pay. Portal.

Cloud Connect supports retrieving payment status after initiating a transaction, allowing the POS system to follow the payment lifecycle.

Refunds

Cloud Connect supports initiating refunds through the terminal flow.

  • ☐ Refund can be initiated.
  • ☐ Correct terminal is selected.
  • ☐ Refund amount is correct.
  • ☐ Refund result is returned correctly.
  • ☐ Refund appears correctly in Pay. Portal.

Customer experience

Although the POS system starts the payment, the customer interacts with the PAy..POS terminal.

  • ☐ Customer clearly knows when to present their card or mobile device.
  • ☐ Payment instructions are visible.
  • ☐ Customer receives feedback during processing.
  • ☐ Successful payments are clearly confirmed.
  • ☐ Failed payments provide clear next steps.

Terminal scenarios

Test different terminal situations.

Available terminal

  • ☐ Payment starts successfully on an available terminal.
  • ☐ Transaction appears on the expected device.

Multiple terminals

If multiple terminals are available:

  • ☐ Correct terminal selection is available.
  • ☐ Payment is sent to the intended device.
  • ☐ Incorrect terminal selection is prevented where required.

Connectivity scenarios

  • ☐ POS system can communicate with PAy..POS through Cloud Connect.
  • ☐ Temporary connectivity interruptions are handled correctly.
  • ☐ Terminal reconnects after losing connection.
  • ☐ Payment status remains consistent after connectivity recovery.

Receipts

Providing a receipt after a successful payment is mandatory. Ensure the receipt flow is correctly implemented and tested before going live.

Required:

  • ☐ Receipt option is available after successful payment.
  • ☐ Receipt information is correct.
  • ☐ Customer receives the receipt successfully.

Application certification

Application certification by Pay. is mandatory before going live.

The certification process verifies that the integration meets Pay. requirements and that payment processing, status handling and terminal communication work correctly.

Test evidence

Collect the following evidence during validation:

  • ☐ Successful payment reference.
  • ☐ Failed payment reference.
  • ☐ Cancelled payment reference.
  • ☐ Refund reference (if applicable).
  • ☐ stats.object value.
  • ☐ Terminal information.
  • ☐ Screenshots/Video of the payment flow.

Go-live checklist

Before activating the Cloud Connect integration:

  • ☐ Terminal connection verified.
  • ☐ Payment initiation tested.
  • ☐ Successful payment tested.
  • ☐ Failed payment tested.
  • ☐ Cancelled payment tested.
  • ☐ Status handling verified.
  • ☐ Refund flow verified.
  • ☐ Receipt flow verified.
  • ☐ Certification completed.
  • ☐ Production configuration verified.