Website payments
See, and refund, the payments your own website takes through the Org API.
If your own website takes payments through Lahuta, they show up in Commerce → Website payments. These are payments for things that aren't in your Lahuta shop: membership dues, donations, deposits. Your developer builds the checkout on your site with the Org API, the buyer pays on a Stripe payment page, and the money goes to your Stripe account.
Sales of your shop products, services and event tickets keep their own order lists, even when your website started the checkout. Product checkouts opened through the Org API appear in Product orders.
Setting this up is a job for whoever builds your website. Send them Take payments on your site.
What each payment shows
Each row shows:
- The payer's name and the payment's status.
- What they paid for. With more than one item, it reads like "Studio membership and 1 more".
- Any extra details your website attached to the payment, like "Membership: Annual".
- The date it was paid, or started if it hasn't been paid.
- The amount.
The page lists your 100 most recent payments.
Payment status
| Status | Meaning |
|---|---|
| Waiting | The payer is on the payment page and hasn't paid yet. |
| Paid | The money has arrived. |
| Expired | The payment page closed without a payment. |
| Refunded | You refunded it. |
Refund a payment
Open the ⋮ menu on a Paid payment.
Select Refund with the amount. It refunds everything not yet refunded.
Confirm with Refund. The money goes back to the payer from your Stripe account. You can't undo it.
Who gets told
When a payment comes in, everyone in your organization gets a notification, including an email headed "Paid on your website" with an Open payments button. Each person can change what they're notified about in Notifications.
The payer is added to your contacts, or matched to their existing record, so the payment appears in their history in the CRM.