Business payment providers

Collections versus platform billing

Open Workspace settings → Payments to configure merchant connections for supported business collection workflows. This is separate from Billing, where you manage your platform plans and credits.

The editor offers Razorpay, PhonePe, Paytm, Stripe and Amazon Payment Services. A listed connection option does not imply that every payment method, country or downstream module workflow is available. Confirm the requirements of your merchant account and intended workflow.

Before connecting

Use workspace administrative access and a merchant account you are authorized to configure.
Confirm the account’s supported payment methods and onboarding requirements with the provider.
Start with the provider’s test environment. Keep test and live credentials separate.

Configure and verify

Select the provider and the Test environment.
Enter the merchant fields shown in the editor, including the signing fields required by that provider.
Choose only the modules that should use this connection for supported collections.
Save the provider configuration, then select Verify connection.
Review the result and validate the intended collection workflow. Configure and verify Live separately before accepting real payments.

Merchant provider tabs, Test and Live environment controls and empty credential fields. — Select the provider and environment before entering merchant credentials. The screenshot shows unconfigured fields, not working credentials.

Prepare the provider-specific fields

Obtain the following labels from your own merchant account for the selected environment. These are field names, not example credentials. The editor identifies which fields are required and which signing fields are recommended.

Copy values only from the merchant account you are authorized to connect.
Check that every value belongs to the selected Test or Live environment.
Enter secrets in the protected fields. If a field is already configured, follow the editor’s guidance for retaining or replacing it.
Save and verify that environment before enabling its supported business collection flow.

Razorpay: Key ID, Key Secret and Webhook Secret.
PhonePe: Client ID, Client Version, Client Secret and Webhook HMAC Secret.
Paytm: Merchant ID (MID), Website Name and Merchant Key.
Stripe: Publishable Key, Secret Key and Webhook Signing Secret.
Amazon Payment Services: Merchant Identifier, Access Code, SHA Type, SHA Request Phrase and SHA Response Phrase.

Connection status and routing

Test and Live are stored and verified independently. A saved configuration may show Test required until verification succeeds. Connected confirms the connection check, not completion of every downstream collection workflow.

Module routing controls where the account may be used. Enabling a module here does not buy its plan or implement a payment workflow that the module does not support.

Supported module routing choices above Verify connection and Save Razorpay actions. — Enable only intended modules. Save the configuration and verify that environment before using supported collection workflows.

If verification fails

Check the selected environment and the provider-specific fields. Retain stored secret fields according to the editor’s guidance; never paste credentials into a support ticket.

For a missing collection option, check module access and the relevant workflow. Use Billing for platform subscriptions and credits rather than changing merchant connections.

Related guides

Plans and bundles

Need help with this workspace?

Ask your workspace administrator for access or contact support with the page name and a sanitized error message.

Collections versus platform billing

Open Workspace settings → Payments to configure merchant connections for supported business collection workflows. This is separate from Billing, where you manage your platform plans and credits.

Configure and verify

Select the provider and the Test environment.

Enter the merchant fields shown in the editor, including the signing fields required by that provider.

Choose only the modules that should use this connection for supported collections.

Save the provider configuration, then select Verify connection.

Review the result and validate the intended collection workflow. Configure and verify Live separately before accepting real payments.

Provider and environmentDemo workspace

Select the provider and environment before entering merchant credentials. The screenshot shows unconfigured fields, not working credentials.

Prepare the provider-specific fields

Copy values only from the merchant account you are authorized to connect.

Check that every value belongs to the selected Test or Live environment.

Enter secrets in the protected fields. If a field is already configured, follow the editor’s guidance for retaining or replacing it.

Save and verify that environment before enabling its supported business collection flow.

Razorpay: Key ID, Key Secret and Webhook Secret.

PhonePe: Client ID, Client Version, Client Secret and Webhook HMAC Secret.

Paytm: Merchant ID (MID), Website Name and Merchant Key.

Stripe: Publishable Key, Secret Key and Webhook Signing Secret.

Amazon Payment Services: Merchant Identifier, Access Code, SHA Type, SHA Request Phrase and SHA Response Phrase.

Connection status and routing

Module routing controls where the account may be used. Enabling a module here does not buy its plan or implement a payment workflow that the module does not support.

Module routing and verificationDemo workspace

Enable only intended modules. Save the configuration and verify that environment before using supported collection workflows.

If verification fails

Check the selected environment and the provider-specific fields. Retain stored secret fields according to the editor’s guidance; never paste credentials into a support ticket.

For a missing collection option, check module access and the relevant workflow. Use Billing for platform subscriptions and credits rather than changing merchant connections.