Create a payment extension app

After passing the payment partner review, you need to create a new application in the Genstore Developer Center and email the following information to paymentdeveloper@genstore.ai:

• Partner name
• Application name
• ClientId

Genstore will complete the authorization within 2 business days, and your application will receive payment extension development permissions.

Create a public application

1. Log in to the Genstore Developer Center, click App → Create app.
2. Enter the application name. This name will appear in the following list:
   • Genstore Merchant Admin → Settings → Payments → More Payment Methods → Third-Party Payment Providers / Other Payment Methods.
3. After the application is created, click into the application configuration page, find Application configuration in the left navigation, and fill in the information:
   • Embed app in Genstore admin must be set to No, otherwise, there may be issues with page nesting and the application may not function.
4. Click Save to complete the configuration.

Request application extension permissions

At this point, your payment extension does not yet have permission. Please send Partner name, Application name, and ClientId to paymentdeveloper@genstore.ai. Genstore will complete the authorization within 2 business days, and after that, you can create payment extensions within your application.

Develop and configure payment extensions

Create a payment extension

1. Log in to the Genstore Developer Center, click the application name to enter the application configuration page.
2. On the Overview tab, click Configure extension information in the App extensions section.
3. Click Create App extension and switch to the Payment extension tab.
4. Click Create now to enter the extension configuration page.

Configure payment extensions

The configuration page for payment extensions is divided into the following sections:

• Payment extension test information:
  • Provide information required for review (e.g., account number, password, test merchant ID, secret key, etc.).
  • Test accounts requiring two-factor authentication must not be provided, as the authorization validation cannot be completed.
• Basic information: Choose the payment extension model (card payment / offsite payment).
• Payment capability configuration: Define payment capabilities (e.g., collection, refund, capture, etc.), how payment methods are displayed, and API endpoint information.

Choose a payment extension model

In the payment extension configuration page, click the Edit button in the Basic information section and select the payment model based on business needs:

• Direct (Card payments): Customers enter card information directly on the checkout page to complete the payment.
• Redirect: Customers are redirected to an external page to complete the payment (which can aggregate multiple payment methods).
  • If multiple methods are supported, Genstore will display a banner for your application on the checkout page. Customers will be redirected to an aggregated payment gateway when they click Pay Now.

TIP

Once the payment extension model is confirmed, it cannot be changed. Please proceed with caution.

Configure card payment extensions

Payment capabilities

Card payment requirements:

• Must implement: capture, refund, tokenization capabilities.
• Optional implementation: void (if supported, must be completed within 7 days and implement reminder and overdue handling logic).
• Tokenization:
  • Tokenization must be implemented, and the public key must be provided in the configuration.
  • Genstore and the payment app will use encrypted communication, and you must implement the specified algorithm (see Encryption Algorithms).

Payment methods

You can offer international mainstream credit cards or regional cards for your merchants, where, except for American Express, the card number, expiration date, and 3-digit CVV must be provided.

Endpoint configuration

In the Endpoints tab, register the API addresses for each capability to allow Genstore to communicate with your extension.

Configure offsite payment extensions

Payment capability configuration

Redirect payment requirements:

• Must implement: capture, refund capabilities.
• Optional implementation:
  • Void
  • Installments

Payment methods

• Multiple methods can be configured: bank transfers, convenience store payments, cryptocurrencies, etc.
• To add additional payment methods or brand logos, please contact paymentdeveloper@genstore.ai.

Endpoint configuration

In the Endpoints tab, register the API addresses for each capability to allow Genstore to communicate with your extension.

Save drafts and testing

• After completing the extension configuration, click Save Draft in the upper right corner to return to the extension list page.
• Enable the Development store preview feature and test the payment extension capabilities using the developer account to ensure it meets merchant needs and Genstore review requirements.

Create extension versions

Once the payment extension passes the developer store verification, you can create an extension version for review:

1. Go to the application details → App extensions. Click the HandleID (unique identifier) for the payment extension.
2. Confirm that the payment extension test information is correctly filled.
3. Click Create version, enter the version name and description.
4. Click Submit and activate version to automatically start the review process.
5. Review results will be sent by email. You can also check the review status in the application details → Version management.

Configure the application and submit for review

Configure application permissions

1. Configure the application’s permissions (refer to Application Permissions Configuration Guide).
2. Payment extension applications only support the following permission scopes:
   • write_payment
   • read_apps
   • write_apps
   • Requests for permissions beyond these scopes will not be effective.

Submit the application for review

After the payment extension review is passed, you can submit the application for review. Once approved, it will appear in the merchant admin’s payment method list. For detailed steps, refer to the Application publishing guide.