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

Full Integrated SDK Validation Checklist for Pay.POS

This checklist helps Product Owners, QA teams and implementation partners validate a Pay.POS Full Integrated SDK implementation before going live.

Purpose

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

Before you start

Complete the Pay.POS: Getting Started & Choosing the Right Integration checklist before validating this 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.

  

Payment screen requirements

The payment screen must contain:


Payment information

  • ☐ Payment amount is displayed.
  • ☐ Currency is displayed.
  • ☐ Amount and currency match the initiated transaction.
  • ☐ A dynamic loader is displayed during payment processing. 

Customer message

The payment screen must provide a clear instruction to the customer during the payment process.

Required:

  • ☐ A customer-facing payment instruction is displayed.
  • ☐ The message clearly explains what the customer needs to do.
  • ☐ The message is visible during the contactless payment step.
  • ☐ The message is available in the required languages (if applicable).

Contactless payment guidance

Customers must clearly understand where to present their card or mobile device.

  • ☐ NFC/contactless indicator is displayed.
  • ☐ NFC placeholder is visible.
  • ☐ Customer knows where to tap their card or phone.

 Branding (Recommended)

  • ☐ Pay. logo is displayed.
  • ☐ Logo is centered at the top of the screen.
  • ☐ Logo is clearly visible and not distorted.

  

The following screenshot shows how Pay. implemented the Pay.POS payment screen.





SDK payment flow validation Starting a payment

Verify that:

  • ☐ Payment can be started from the merchant application.
  • ☐ The correct amount is shown.
  • ☐ The correct currency is shown.
  • ☐ The payment flow starts without additional manual actions.

Customer payment experience

Test the complete customer journey.

Physical cards
  • ☐ Contactless debit card payment succeeds.
  • ☐ Contactless credit card payment succeeds.
Digital wallets
  • ☐ Apple Pay payment succeeds.
  • ☐ Google Pay payment succeeds.
Payment result
  • ☐ Successful payment result is returned correctly.
  • ☐ Transaction status matches the result shown in PAY.POS.
  • ☐ The merchant application continues after completion.

Payment interruption scenarios

Validate how the application handles unexpected situations.

Customer actions
  • ☐ Customer cancels the payment.
  • ☐ Customer removes the card too early.
  • ☐ Customer does not complete the payment.
Application behaviour
  • ☐ Application receives the correct status.
  • ☐ User receives clear feedback.
  • ☐ Payment can safely be retried.
  • ☐ No duplicate payment is created.

Device and connectivity scenarios

Test the behaviour in different situations.

Connectivity
  • ☐ Temporary internet interruption tested.
  • ☐ User receives clear feedback.
  • ☐ Transaction status remains consistent.
Device
  • ☐ NFC disabled scenario tested.
  • ☐ Device restart scenario tested.
  • ☐ Application restart scenario tested.
  • ☐ Unsupported device scenario handled correctly.

Additional functionality

Validate optional features if enabled.

Important

Providing a receipt after a successful payment is mandatory. Make sure the customer always has the option to receive a receipt and that the receipt flow is correctly implemented and tested before going live.

Receipts
  • ☐ Receipt generation works.
  • ☐ Receipt information is correct.
  • ☐ Customer receives the receipt.
Refunds
  • ☐ Refund can be initiated.
  • ☐ Refund amount is correct.
  • ☐ Refund result is handled correctly.
  • ☐ Refund appears in Pay. Portal.

Offline payments (MAT)

  • ☐ Offline scenario is tested.
  • ☐ Merchant understands offline payment limitations.
  • ☐ Transactions are processed correctly once connectivity returns.
  • ☐ The terminal clearly indicates when closing that there are still payments in the queue.
  • ☐ It is possible to sync transactions individually.
  • ☐ It is possible to sync all payments with a delay of at least 1 second.

Test evidence

During validation, collect:

  • ☐ Screenshot of the payment screen.
  • ☐ Successful transaction reference.
  • ☐ Failed transaction reference.
  • ☐ Cancelled transaction reference.
  • ☐ stats.object value.
  • ☐ Device information.

Go-live checklist

Before activating the SDK integration:

  • ☐ All minimum requirements completed.
  • ☐ Payment flow tested end-to-end.
  • ☐ Error scenarios tested.
  • ☐ Refund flow tested (if applicable).
  • ☐ Production configuration verified.
  • ☐ Application certified by Pay.

Important

Application certification by Pay. is mandatory before going live. The certification process verifies that the integration meets Pay. requirements and that the payment flow, user experience and transaction handling work correctly.