UlasendUlasendDocs
Overview

Store integrations

Connect a storefront to Ulasend with a platform plugin or a server-side API integration.

These integrations are development previews. The first release focuses on one-time USD orders paid through a USDC on Base checkout. Recurring billing, saved cards, automatic refunds, and bank-transfer checkout are unavailable in these integrations. Each platform must be tested with its own order, stock, email, and fulfillment configuration.

Choose your platform

  • WooCommerce: a downloadable WordPress plugin for staging tests, with classic checkout, Checkout Blocks, and HPOS support.
  • GoHighLevel: a connector requiring Ulasend app configuration and testing with an authorized location before activation.
  • Shopify: review the adapter groundwork and required approvals. Merchant installation is not yet available.
  • Custom storefronts: use the Node.js SDK or the invoice API in your own server integration.

Downloads and sharing

These guides and downloads are public and can be shared with your store developer. Download the WooCommerce plugin 0.1.0 or Node.js SDK 0.1.0. Each includes setup instructions. GoHighLevel and Shopify do not have an installable download in this release.

Developers can check the published SHA-256 manifests for the plugin and SDK. Keep API keys and signing secrets private when sharing a guide.

How an order is paid

  1. Your store calculates the order total on its server.
  2. The integration creates an invoice and saves its identity and final quoted amount with the order.
  3. The buyer completes hosted checkout.
  4. The integration verifies current payment evidence and updates the matching order once.

The hosted quote includes any processing fee passed to the buyer and conversion rounding. It can exceed the store's original USD total. The full final quote must be received before fulfillment, even if your account permits small crypto shortfalls. A success page is not proof of payment. Pending, partial, mismatched, and late payments need reconciliation.

Start in a local or staging store and keep test stock, emails, and fulfillment separate from real orders. Use the Integrations dashboard for downloads and your merchant ID, and Developers for API keys and webhook settings. Existing payment processing and receiving-wallet requirements still apply; see the account and wallet setup guide.