PathwAI's Authorize.Net integration lets the Payment block take cards through Authorize.Net instead of Stripe. Card details are tokenized in the browser by Authorize.Net's Accept.js. PathwAI's server then either creates a customer profile with the saved card, or creates the profile and charges the amount set on the step. The result, including the transaction ID for a charge, is saved on the submission.
What data moves
- Browser to Authorize.Net: the card details, which Accept.js turns into a one-time token, so the card number does not pass through PathwAI.
- PathwAI to Authorize.Net: the token, the customer email, the billing name and address and, for a charge, the amount.
- Authorize.Net to PathwAI: the status, customer profile ID and payment profile ID, and for a charge the amount, currency and transaction ID. Card numbers are never saved in the answer.
- PathwAI to your tracking: a successful charge produces a purchase event with value, currency and order ID.
Where it is configured
Integrations → Authorize.Net holds the API login ID, transaction key and public client key, stored separately for Sandbox and Production. Each Payment step picks Authorize.Net as its processor and sets the environment, mode, amount, customer email and billing address.
Use cases
Keep an existing merchant account
Programs that already process through Authorize.Net take payment inside the intake flow instead of sending people to a separate payment page.
Card on file before review
Save card creates a customer profile without charging, so the card can be charged after a clinician reviews the intake.
A fixed fee at the end of eligibility
Charge now creates the profile and charges the amount set on the step in one request.
How to set it up
- In Authorize.Net, collect the API login ID, transaction key and public client key for sandbox and production.
- In PathwAI, open Integrations → Authorize.Net and paste them for each environment.
- Add a Payment step and choose Authorize.Net as the processor.
- Map the billing name and address to earlier answers, or turn on Collect billing address on form.
- Test in Sandbox, then switch the step to Production before you publish.
Good to know
- Authorize.Net in Production needs a billing address, either mapped from an earlier Address step or collected on the card form.
- The step saves a card or makes a one-time charge. Recurring billing, refunds and voids are handled in Authorize.Net.
Authorize.Net integration FAQ
Does card data pass through PathwAI?
Card details are tokenized in the browser by Accept.js. PathwAI's server receives the token, not the card number, and the saved answer holds only Authorize.Net IDs, the status and the amount.
Can one workspace use Authorize.Net and Stripe?
Yes. Each Payment step chooses its own processor, and the keys for each processor are stored separately in Integrations.
Which currencies are supported?
The Payment step offers USD, EUR, GBP, CAD and AUD for a charge.
Want to see Authorize.Net in a flow?
We can walk through where Authorize.Net fits in your funnel and exactly which data it would receive.