Maxana Developer Documentation

There are two end-to-end integrations. Choose the reader you are and stay in that tutorial. Both tutorials point to the same reference when a contract needs to be looked up.

Choose your tutorial

Direct merchant developerYour business signs up with Maxana, connects its own PayPal account, and takes payments for itself.→Channel developerYour platform provisions and operates every merchant with one channel credential.→

A merchant acquired through a channel does not use this portal or a Maxana dashboard. The channel builds that merchant’s integration, including the buyer checkout. A direct merchant builds only for its own business.

Keep credentials server-side

In both tutorials, browser code receives a checkout-session identifier or URL, never a merchant or channel secret.

Shared reference

The reference is for lookup, not a third journey. It contains the shared authentication model, checkout-session contract, SDK options, error codes, webhook payload and delivery contract, and generated API operations.

Current limits

This portal does not create accounts, provision merchants, or replace either reader’s dashboard and server-side integration. The published maxanapay.js SDK supports the PayPal wallet rail; the direct-merchant tutorial identifies when Hosted Checkout or Embedded Checkout is required for another production capability.