Verify the Integration Before Building
This check exists to find those hard-to-trace problems early. It only reads your project. It does not change any files, build anything, or run your app. It's run right after adding or changing a payment module, before building the app.
-
Confirms the Nuvei payment layer is on disk - The payment code is in place. It confirms that the Nuvei payment files were written into your project.
-
Confirms the Nuvei SDK is added as a dependency in your build - Your app needs to declare the Nuvei SDK before it can use it. This check confirms that has happened, and tells you exactly what is missing if it has not.
-
Confirms the network settings needed to talk to the backend are in place - If your backend runs on your own machine for testing, your app needs permission to reach it. This check confirms that permission is in place and properly linked. If your backend is a secure remote server, no special permission is needed, and the check accounts for that.
-
Confirms your app's theme is compatible with the checkout screen - The Nuvei checkout screen is built on standard design components, and if your app's theme does not support them, the checkout screen closes the moment it opens. This is one of the harder problems to trace, because nothing goes wrong until the exact moment a customer tries to pay. This applies to Android apps, and it is reported as a warning rather than a blocker, so you stay in control of your app's appearance.
-
Confirms the app starts up the Nuvei SDK when it launches - The SDK has to be initialized once when your app launches. If that step is missing, your app will still build without any error, but every payment will fail. This check confirms the start-up step is in place.
-
Gives a plain list of what is left to do if anything is missing - You get back a clear result: either your app is ready, or a short list of what is still missing, written in plain steps you can act on. Nothing is hidden behind technical output, and nothing is left for you to guess at.