🚧

Private Beta

This is a private beta version of Shoplazza's Payments Apps APIs. The documentation will be updated as we introduce new features. For access to this beta, please review the process of building a payments app and having it approved by Shoplazza Review Team.

Payment apps are public apps that integrate with the Shoplazza to provide payment processing services. Only approved partners will be able to build payment apps on Shoplazza's Payment Platform.

Using a payment app, merchants can redirect buyers to an app-hosted page for payment processing, which may include the following payment methods:

• Wallets
• Buy Now Pay Later / Installments / Buyer Financing
• Cards
• Bank Transfers / Online Banking
• Cryptocurrency
• Cash + ATM

The payment methods support the following operations:

• Charge: Partners can collect a buyer's payment information and charge them for their purchase
• Refund: Merchants can trigger a refund from their Store Admin
• Authorize: Merchants can place a hold that can be charged at a later time
• Capture: Merchants can charge the amount previously specified via an authorization
• Void: Merchants can cancel a previously authorized amount

Merchants decide whether they prefer to capture funds at the time of purchase or at the time of fulfillment.

Payment App requirements

The following list of requirements outlines the minimum product requirements for building payment apps. Failure to meet these requirements may result in:
• Removal of your app from Shoplazza’s public list of payment gateways.
• Suspension of access to the Shoplazza payment ecosystem.
• Termination of participation in the payment ecosystem.

Partners building payments apps need to consider the following requirements:

• Merchant discovery - To qualify for inclusion in Shoplazza’s public list of payment gateways, payment apps must meet the following criteria:
  Usage: The app must be actively used by at least 50 Shoplazza stores.
  Transactions: The app must process at least $1,000,000 USD in transactions.
  Once these conditions are met, partners can apply for inclusion. Shoplazza will evaluate applications and decide eligibility for the public list.

• Approval process required - To make sure merchants can present a positive buyer experience, any app configurations must be approved by Shoplazza. All apps must also be approved before merchants can install them.

• Minimum product requirements - Payment App must adhere to technical requirements and provide a high-quality merchant experience as described in the minimum product requirements.

Minimum product requirements

Feature requirements

Payments apps have the following feature requirements:

• They need to implement the ability for a merchant to charge, refund, and process test transactions.
• They need to be 3DS compliance if they're processing credit card payments in specific countries.

Technical requirements

• Idempotency: To provide a consistent customer experience, payments apps must implement idempotency.
• Retry policy: In case of network errors, payments apps must retry their requests according to the retry policy.
• Mutual TLS (mTLS): Authentication must be implemented to guarantee that traffic is secure and trusted in both directions between Shoplazza and your payments app. This authentication allows your app to confirm if an upstream request has originated from Shoplazza.
• Rate limiting: Your app's OpenAPI requests are rate limited according to the rate limiting guidelines.
• API Versioning: Partners must implement a supported version of Shoplazza's Payments Apps APIs. Partners can configure the API version that their payments app will use to receive requests from Shoplazza. Partners must use the same API version for sending requests. API versions are updated in accordance with Shoplazza's general API versioning timelines.
• 3-D Secure: If you offer credit card payment methods in a country where 3-D Secure authentication is mandated, then you must support 3-D Secure authentication.

Merchant experience requirements

Payment apps must:

1. Maintain 24/7 operational availability with a minimum 99.95% uptime during any measurement period.
2. Respond to outages or technical issues within 2 hours.
3. Offer servicing support to all merchants to resolve problems promptly.