FAQ

UAT (User Acceptance Testing) credentials are used for testing your Miniapp in a sandbox environment. They allow you to test all features without affecting real users or processing real transactions. Production credentials are used for your live Miniapp and process real transactions with actual money. Always test thoroughly with UAT credentials before moving to production.

The documentation you're reading and the Miniapp system as a whole are specifically designed for building Miniapps within Super Qi. This is a different system from the standard Qi Payment Gateway integration.

Miniapps use an internal payment system that is built into the Super Qi platform. If you're looking to integrate directly with the Qi Payment Gateway (outside of the Miniapp context), that is managed by a separate team with different documentation and integration procedures.

To get in touch with the Payment Gateway team and obtain the necessary contact information and documentation for standard payment integration, please contact your account manager. They will provide you with the appropriate team contacts and resources for your integration needs.

The security review process typically takes anywhere from a few days to a couple of weeks, depending on the complexity of your Miniapp and the current review queue. The security team will thoroughly test your Miniapp's functionality, security, and compliance with Super Qi guidelines. You'll be contacted if they have any questions or concerns during the review.

Yes! You can create new versions of your Miniapp at any time. Simply create a new version in the Super Qi Console with your updated code, test it thoroughly with UAT credentials, then submit it for release following the same process.

If you've committed credentials to Git, immediately rotate your credentials by contacting the Miniapps team. Remove the credentials from your repository history using tools like git filter-branch or BFG Repo-Cleaner. Never reuse exposed credentials, even if you delete them from your repository.

There are many factors in UAT that can cause "Operation Failed" errors. First, make sure you have the following configured correctly: you're using the latest UAT version of the Super Qi app, your environment is set to UAT (not Production), and you're logged into one of the KYC accounts we provided for you. If you're developing and testing your Miniapp and still getting "Operation Failed", please ensure your phone and machine are on the same network, and verify that the Miniapp version you're testing is configured for UAT (not Production) since you're testing in the UAT environment. If problem still persists, then please contact the Miniapp team.

No, you can use the same credentials since you are the same merchant

Cashier payment (CASHIER_PAYMENT) is a one-time payment where users authorize each transaction individually by scanning a QR code or payment link. Agreement payment (AGREEMENT_PAYMENT) is a recurring payment setup where users grant permission once, and your Miniapp can charge them in the future without additional authorization. Agreement payments are ideal for subscriptions and recurring billing, while cashier payments are better for one-time purchases. Keep in mind that the agreement payment requires a special scope

Super Qi supports two distinct user types, each with their own set of authorization scopes:

Customer User Scopes are used when your Miniapp needs to access information about individual end-users (consumers). These scopes allow you to retrieve personal information such as user ID, name, avatar, contact information, and preferences. Use Customer scopes when building Miniapps for regular consumers, such as shopping apps, food delivery services, or entertainment platforms. Examples include: USER_ID, USER_NAME, USER_AVATAR, USER_CONTACTINFO, and auth_base.

Business (Merchant) User Scopes are used when your Miniapp needs to access information about business users or merchants on the platform to make purchases. These scopes are designed for B2B scenarios where one merchant needs to interact with another merchant and buy their products or related reasons. They allow you to retrieve business-specific information like merchant ID, business name, and merchant logo. Use Business scopes when building Miniapps that facilitate business-to-business transactions. Examples include: MERCHANT_ID, MERCHANT_NAME, MERCHANT_LOGO, and auth_base (for merchants).

Important: You must use the appropriate scope type based on your target audience. Attempting to use Customer scopes to retrieve Business user data (or vice versa) will fail. For a complete list of available scopes, see the getAuthCode Scope Reference.

All monetary values in payment APIs must be expressed in fils, which is the smallest currency unit of IQD (Iraqi Dinar). Since 1 IQD = 1000 fils, you need to multiply your IQD amount by 1000. For example, 150 IQD should be sent as 150000 fils. This applies to all payment-related API endpoints including pay, inquiry, and refund operations.