Four MemberArea steps turn a conversation into a sale or an unlock. Two of them sell: Send checkout link and Get order status. Two of them hand out access directly, without a payment: Grant access and Revoke access.
Permissions the API key needs
Each step checks the permissions of the API key in the app settings:
| Step | Permissions |
|---|---|
| Send checkout link | Payments: View |
| Get order status | Payments: View |
| Grant access | Payments: View and Manage, Members: Manage |
| Revoke access | Payments: View and Manage |
View is needed for the Product list, because Manage does not include it. A key at Full access covers all four. If a step answers "This ManyChat connection is not allowed to run this step", the key is missing one of these.
Send a checkout link
Send checkout link builds a link to the checkout page of one product, ready to put in the next message.
- Add the step and pick the product under Product. The list offers active products only.
- Leave Quantity empty for one piece, or enter a number up to 99.
- Map Checkout url into a custom field and send it in a button or a text.
The link is personal. It carries the email address and the name your memberarea knows for this subscriber, so the checkout page opens with both already filled in. The order is linked to the member or contact behind the chat.
The step also sends back the price, so the message can name it before anyone clicks. Price formatted is the main price of the product, written out in the language of your memberarea, for example "49.00 EUR". A price without tax carries "plus VAT".
The step refuses when the link could not work:
- "This product cannot be bought right now because it is inactive or has no active price." Activate the product or give it an active price.
- "This MemberArea has no web address yet, so no checkout link could be built." Set the domain in your settings first.
What the buyer sees
The buyer taps the link and lands on the normal checkout page of your memberarea, with the same prices, payment methods and order bumps as anyone else. Paying there creates a regular order: the buyer gets access, the receipt and every email your memberarea sends after a purchase.
The chat does not wait for the payment. To answer after the purchase, build a second flow that starts with the Order paid event. Starting a flow from your memberarea explains how.
Check the order status
Get order status reads the latest order and the current subscription of this person, so a flow can answer "did my payment go through?" on its own.
Leave Order empty to read the latest order. Test purchases and drafts do not count. An order from another person is never shown: the step then answers "This order does not belong to this person or no longer exists."
The most useful values:
- Found tells whether the person has any order or subscription at all.
- Has paid order tells whether the person has paid at least one order.
- Order number, Order status and Order total formatted describe the latest order, ready for the message.
- Has active subscription and Subscription status describe the subscription. An active subscription comes first, otherwise the latest one.
- Subscription renews at formatted and Subscription ends at formatted say when it renews or ends, in the language and time zone of your memberarea.
Grant access without a payment
Grant access gives the person everything that belongs to a product or a bundle: courses, groups, calendars, events, badges and whatever else the product unlocks. Pick it under Product, or pick a whole bundle under Or bundle. When both are filled, the product wins.
- If the person has no account yet, the step creates one. Member created then says so.
- No order is written. The access appears on the member, not in your sales.
- Running the step twice is harmless. Newly granted counts only what was new, and Access items names everything the product covers.
A product that is still a draft is refused with "This product is still a draft in your MemberArea, so no access was granted." When your plan allows no more members, the step answers "This MemberArea has reached the number of members its plan allows, so access could not be granted."
Revoke access
Revoke access takes back what a product or bundle gave. The account itself stays, and so does anything the person also has from a paid order, even a paid order of this same product. Only access that no paid order covers goes away.
Newly revoked counts what was removed. If the person has no member account, the step answers "This person does not have a member account in your MemberArea, so there was no access to remove." and nothing changes.