PaymentIQ login, documentation & support.

Open the official documentation

The current PaymentIQ homepage labels its link to docs.paymentiq.io “PaymentIQ Login”. This is the documentation destination linked by the vendor; it should not be assumed to be a universal back-office login. Some documentation requires an authorised account.

• Open official documentation (opens a new tab)
• Visit the official PaymentIQ website (opens a new tab)

Access your back-office account

Use your organisation’s approved bookmark or the address in your onboarding instructions. Check that you are using the intended environment and account. Access permissions and password resets belong with your organisation’s administrator or your PaymentIQ contact.

• Confirm whether you need documentation access, a test environment or the production back office.
• If a colleague can access the same environment, compare the account permissions and access requirements with your administrator.
• If several users are affected, record the time, timezone and exact browser error before escalating.

If you can sign in but a payment still fails, use the PaymentIQ failure investigation checklist.

Public guides and integration tools

For implementation research, these vendor resources provide a useful starting point. Follow your team’s process for handling credentials and selecting the correct environment.

• PaymentIQ public integration guides (opens a new tab)
• PaymentIQ cashier configuration sandbox (opens a new tab)
• PaymentIQ Hosted Fields SDK (opens a new tab)

Checking PaymentIQ service status

Use the service-status link or support channel provided to your organisation. This page does not monitor PaymentIQ or show live incident information. A failed payment alone does not establish a platform outage: the symptom may concern a provider, a method, the cashier or a particular transaction flow.

• Check whether the issue affects one provider or several, and one payment method or several.
• Compare the time of the first failure with the official incident information available to your team.
• Keep the browser or payment error separate from assumptions about its cause.