AroFlo Booking Forms

Connect Stripe so AroFlo booking forms can take payments

3 min read AroFlo booking form

The Stripe keys on this page are the account-wide Stripe connection for every AroFlo booking form that takes payments. A form only uses them once payments are switched on under Payments.

Before you start

  • Payments need a booking form subscription. The page says "Stripe credentials are used for forms that have a payment option (subscription required)."
  • You need a Stripe user who can open Developers and API Keys.

Step by step

  1. Click Settings in the AroFlo Bookings menu, then Stripe under Form Setup.
  2. Paste the Stripe Publishable Key and the Stripe Private Key. Both are required.
  3. Click Test Publishable Key and Test Private Key if you want to check them first.
  4. Click Create Stripe credentials. When the account already has a Stripe credential the button reads Update Stripe credentials.

Both boxes are plain text, so the private key is visible while you type. Each test button is greyed out while the other key's box is empty.

If you already have Stripe credentials under Integration Credentials, a Stripe Credential dropdown appears above the keys. Choosing one fills in both of its keys. Saving then links that credential to your AroFlo booking forms. A new one is saved as "Stripe integration for AroFlo Bookings".

Using a restricted key

The page offers a standard secret key as the simple option. For a restricted key, create it in Stripe with the key name Formpiece and these permissions:

Permission Level
Charges Write
Customers Write
Payment Intents Write
Payment Methods Read

What the tests do

Test Publishable Key asks Stripe from your browser whether it accepts the key. A 401 or a server error from Stripe shows "Stripe public key is NOT valid." Any other reply shows "Stripe public key is valid."

Test Private Key saves the credential first, then asks the Formpiece API to list customers with the key. It shows "Stripe private key is valid." when that works and "Stripe private key is NOT valid." when it does not. It does nothing until a credential has been chosen or created, so create the credentials before you click it.

What saving changes

Saving updates the credential and names it as the one every AroFlo form takes payments with, then shows "Stripe credentials updated". Every published AroFlo form that takes payments is published again with the new publishable key. The private key is not put on the form.

If a form can't be published again, the credential is still saved and the page lists the form by name with "Use Publish again on it to try again." If none could be, it says "The Stripe credentials were saved, but the forms could not be published again. Use Publish again on each form that takes payments."

When it goes wrong

Bookings fail after a key was changed in Stripe

Keys that Stripe no longer accepts stop payments. Paste the current keys here and save.

"Stripe public key is NOT valid." after a test

The key was rejected with a 401, or Stripe returned a server error. Copy the publishable key from Developers, then API Keys, then Standard Keys in Stripe and test again.

Test Private Key does nothing

No Stripe credential exists yet. Click Create Stripe credentials first.

"Could not update the Stripe credentials."

The credential could not be saved. Check the keys and try again.

"Your Stripe and Square credentials could not be loaded."

Reload the page. Nothing has been changed.