Tools
Payments
A shop or a booking page can take payment with a checkout you connect. The money goes to your payment account. Build3 does not take a cut, and it does not hold the money.
Two different payments
Buying Build3 credits is not the same as taking payment on your site. Credits pay for builds and unlocks. In Nigeria that checkout is Paystack. Everywhere else it is Paddle. Those credits land on your Build3 account.
A checkout on the website you built is yours. Customers pay you. Build3 has a Paystack skill the chat can use. You can also ask it to connect a payment provider you already use.
What to ask for
Say that the page should take payment, and say what the customer is paying for. “A shop with three products, prices, a cart, and a checkout.”
Ask for the checkout. A button that only opens a chat to arrange payment is not a checkout. If you want the Paystack skill, say Paystack. If you want a different provider, name it. A public key can go in the conversation. A secret key cannot.
The secret key
Put the secret key in the Secrets tab, under the name the chat asks for. Then tell the chat you added it. Do not paste the secret into the chat.
With the Paystack skill, that name is PAYSTACK_SECRET_KEY. The chat gives you a webhook URL to put in the Paystack dashboard so a paid order can be confirmed. Copy the URL it shows you.
Your own provider works the same way. The secret stays in Secrets. Use the name the chat asks for, and follow the webhook or confirm step it gives you.
Keep the orders
A checkout that only remembers the order in the browser can lose it. If you need the order after they close the tab, activate the database first, then ask the chat to save orders there.
You read saved orders in the Database tab. Try a test payment before you publish. Publish when the checkout behaves the way you want.