Payment gateways

Payment gateways collect funds for direct customer purchases. Use InAppify's gateway or connect a gateway belonging to your business. Gateway credentials are separate from Bazaar and Myket purchase-verification keys.

Choose a payment path

• InAppify gateway: payments use the platform gateway. See gateway revenue and settlements for financial handling.
• Your merchant gateway: enter your own merchant credentials. Payouts follow your provider agreement and procedures, not InAppify gateway-revenue settlements.
• Store purchases: Bazaar and Myket require their own app configuration. Adding a bank gateway does not replace it.

Merchant-gateway prerequisites

Create a project, obtain valid merchant credentials from your provider, and ensure you have permission to manage project gateways. Your account plan must also enable the own-gateway capability. For upgrade messages, check account feature capacity.

Before a live purchase, configure a custom payment domain, verify DNS, and activate HTTPS. Gateway selection does not choose project merchant gateways without a ready domain. It may fall back to the enabled default InAppify gateway when available.

Add a gateway in the dashboard

1. Select the intended project in the project selector.
2. Open Project settings → Payment gateways → Add gateway.

3. Select the provider. Current options include ZarinPal, PayPing, Zibal, NextPay, PayStar, and Jibit; the options available in your dashboard are authoritative.
4. Enter a recognizable name, such as “Web sales gateway”. This labels the configuration within the project.
5. Copy the gateway key from the provider's merchant account. It is not an InAppify SDK key or secret REST API key.
6. Enter the gateway secret if required by your provider, then save. Credential names and requirements vary by provider; consult its documentation rather than guessing values.

Enable and choose a default

Select a gateway's name to open its details. Editing lets you manage its name, credentials, and enabled state. Masked credentials are not empty fields; do not submit a masked value as a replacement credential.

Use the gateway's actions menu and choose Make default. Enabled and default are separate settings: a disabled gateway is not selected for purchases, even when marked default.

When an offering has gateway-selection rules, an eligible enabled rule-selected gateway is considered first. Otherwise, selection checks the enabled default merchant gateway for the project with a ready domain, then the enabled default InAppify gateway. A default marker alone does not mean every purchase uses that gateway.

Test before release

• Confirm the custom domain is active and secure.
• Check merchant credentials, enabled state, and default selection.
• Make a test purchase through the app or payment link your customers will use.
• Check bank redirection, app return, and the final purchase state. Returning from the bank alone does not prove success.
• Confirm successful purchases grant the intended entitlement. Follow the purchase test guide.

Common problems

• Missing add/edit actions: check the selected project and collaborator permissions.
• Merchant gateway not selected: check enabled state, default or offering rules, and domain DNS/HTTPS readiness.
• Provider connection errors: verify credentials and merchant-account readiness with the provider. Coordinate callback-domain or source-IP restrictions with support when applicable; connecting a domain does not change server outbound IP addresses.

Change or remove a gateway

Prepare a working alternative before disabling or deleting a gateway, and review offering rules referencing it. Take care with purchases already in progress. Never publish gateway credentials in apps, screenshots, or source repositories.