Welcome to Launchpay

Welcome to the Launchpay Developer Portal. This page orients you to the platform, explains how the pieces fit together, and points you to everything you need to plan and build your integration.

How Launchpay works

Launchpay is Infinicept's PayFac-as-a-Service product. You embed payments and merchant onboarding into your software without becoming a payments company: you set your own pricing and integrate only the parts you need through the UI or the API, while Infinicept handles underwriting, risk monitoring, compliance, and more.

Integration Paths

Prerequisites

Before you start building, you'll need:

• Sandbox credentials, which our team sets up for you.
• The API documentation for the products you're integrating to.
• Familiarity with REST APIs, JSON, and webhooks.

How to get access

Sandbox access is granted by our team. After your environment is set up, you'll receive:

• Your sandbox credentials.
• Your custom field mapping for application testing, if you're using the Partial Application Submit API.
• API keys and webhook subscriptions for your test environment (generated by our team and delivered to you securely) if you're integrating to New Accounts and/or Backoffice via API.

When you are ready to go live, your production credentials and configuration are provisioned the same way. All of the reference documentation is available in this portal, allowing you to explore the products relevant to your integration even before you have credentials. You only need provisioned access to make calls. Our team is here to help with any questions along the way.

Authentication

Authentication differs by product, so always follow the authentication section of the reference for the product you're integrating. In general, the Orchestrate APIs use a token-based flow, while the New Accounts and Backoffice APIs authenticate with API key credentials passed in request headers or request body.

See New Accounts Authentication and Backoffice Authentication for details.

Environments

Launchpay provides separate sandbox and production environments. Build and test against the sandbox first, then move to production once your integration is certified.

For Orchestrate, the sandbox base URLs are:

• Transaction Processing API: https://sandbox-gtw.softpoint.io/api/locations/
• Terminal Cloud API (card-present): https://sandbox-api.softpoint.io/interface/v1/locations/
• Hosted iFrame: https://sandbox-iframe-gtw.softpoint.io/

Production base URLs are provided with your production credentials.

Your New Accounts and Backoffice environments are hosted at URLs created specifically for your program. Our team will share these along with your credentials.

Webhooks

New Accounts webhooks and Backoffice webhooks allow your system to receive events as they happen, instead of polling for updates. The events available to you depend on your integration. For example, transaction and funding events for payment processing, or merchant onboarding events if you've integrated to New Accounts via API.

Testing

Test thoroughly in the sandbox before requesting certification. Aim for a solution you'd be comfortable handing to a customer.

Test cards are available for simulating card transactions, including different approval and decline scenarios. Be sure to test edge cases (for example, attempting to refund more than the original transaction amount) so your solution handles them gracefully.

Errors and responses

Your integration should distinguish a declined transaction from a system error and handle each appropriately. See New Accounts API Status Codes, Backoffice API Status Codes, and the API Reference and for the response structure and the codes returned for successful, declined, and error responses.

Next steps

1. Confirm your four integration choices with our team.
2. Explore our Guides and API Reference for the products you're integrating.
3. Once you receive your sandbox credentials, build and test your integration.
4. Follow the Launch Checklist to move from build to certification to going live.