Launch Checklist

The launch checklist outlines the prerequisites to launching with , including operational and developer-specific tasks.

Please note that this checklist can be updated at any time to reflect new requirements or processes.

Operational Tasks

The operational tasks below are required before launching with :

• Submit the Partner Application:The partner application provides with insight into your business and processing requirements.
• Sign the Partner Processing Agreement:Review and sign your agreement with , which includes your buy-rates and revenue share for commission purposes.
• Submit W9 and Voided Check:A W9 and Voided Check (or Bank Letter) are required before receiving your first commission payout. If providing a Bank Letter, it needs to be dated within the last 30 days.
• Set up merchant pricing:Align on your pricing strategy and configure your pricing templates.
In addition, we recommend you complete the following:
• Invite team members:Invite additional team members configure your pricing templates to access the .
• Configure white-label:Configure your white-label settings to maintain brand consistency across the merchant journey.
• Customize merchant preferences:Customize merchant preferences if leveraging no-code modules.
• Request a SaaS account:A merchant account is required if you intend to process your platform's SaaS fee payments through .
• Order terminals:Order developer terminals if planning to support in-person payments.

Developer Tasks

The developer tasks below are required to be completed in before launching with :

• Create API Keys:Create your secret and publishable API keys in order to access API.
• Submit a merchant application:Submit a merchant application using the OnboardingAPI or through the .
• Collect a payment:Collect a payment using the Payment IntentsAPI or or through the .
• Initiate a refund:Refund a payment using the Create a RefundAPI endpoint or through the .
• Build a checkout form:Build a custom checkout form using Payments.jsJS.
• Configure webhooks:Configure webhooks to receive real-time notifications about events occurring on platform.
• Share checkout flow:Provide a live demo of your final checkout flow to our Integrations team, or share access to your demo environment by emailing . This ensures we can review network and console logs, which are not visible in video submissions, for compliance and functionality.
Depending on your integration, you may also need to:
• Collect a platform fee:Include a platform_fee_amount when Creating a Payment IntentAPI.
• Collect a payment using a stored payment method:Attach a Payment Method to a CustomerAPI and Create a Payment IntentAPI using the stored payment method.
• Create a checkout session:Generate a checkout_session_url using the Create a Checkout SessionAPI endpoint.
• Set up a subscription:Set up a subscription to charge customers on a recurring basis.
• Simulate a dispute:Simulate a dispute and submit dispute evidence using the DisputesAPI or through the .
• Create shared payment methods:To share payment methods across merchants, Create a Payment MethodAPI using the partner account_id.