Connecting PaymentIQ: what to check before launch.

1. Decide which payments you want to offer

Start with the countries, currencies and payment methods your customers need. An API is the connection that lets systems exchange information; the cashier is the screen where the customer makes a payment.

• List the deposits and withdrawals you need to support.
• Identify who looks after your website, the cashier, PaymentIQ and each payment provider.
• Agree which tests must pass before launch.

2. Check that the customer is recognised

When someone opens the cashier, the systems need to know which customer is making the payment. A session is the temporary link to that customer's signed-in account.

• Check that the payment screen opens for the correct customer and currency.
• Test what happens when the customer has been inactive and their session expires.
• Check that test settings are used for testing and live settings for real customers.

A test payment is failing? Read how to find the cause.

3. Check which provider receives the payment

A payment service provider, or PSP, processes the payment. Routing rules decide which provider and account PaymentIQ should use. For example, a business may use different providers for different countries or currencies.

• Check that the expected payment methods appear for the customer.
• Compare the provider selected in the transaction with the provider you expected.
• If you use a backup provider, check when the rules allow it to be used. Do not assume every refusal should be retried.

4. Test what happens after the customer clicks Pay

A success message on the screen is only one check. Confirm what is recorded in PaymentIQ and in your own platform. For a successful deposit, check that the customer's balance is updated correctly.

• Test successful, refused, cancelled and pending payments where the method supports them.
• Check interrupted bank redirects and repeated clicks for unwanted duplicate actions.
• Agree who will monitor the launch and how to return to the previous setup if needed.

5. Give developers the right documentation

This guide explains what to check. Your developers need the official documentation for the exact API fields and setup instructions.

• PaymentIQ documentation (opens a new tab)
• Official PaymentIQ website (opens a new tab)
• Hosted Fields developer documentation (opens a new tab)