Access and gates

set_paid_access

Create or update one paid access offer (GBP only): omit offer_id to create, pass it to update. protected_paths is a FULL REPLACEMENT, selected_pages only. access_days sets the access length in whole days, or null for lifetime. buyer_audience picks the checkout compliance flow: consumers_allowed (default on create) keeps the consumer disclosure and cancellation layer and requires the account's public seller details (get_seller_details / set_seller_details) before a live offer is accepted; business_only asks the buyer to confirm a business purchase instead and needs no seller address. Pick it from who the creator actually intends to sell to, never to bypass consumer rules. Omitting buyer_audience on update leaves it unchanged. Side effect: saving a SITE-WIDE offer (entire_site or except_homepage) also makes paid the site's configured primary gate, so a separate set_gate_access is not needed; selected_pages offers never change the primary gate, and archiving the last site-wide offer falls back to the stored classic gate. publish_site is still required before visitors see it. Buyer requirements: set_paid_access_requirements and set_paid_access_password. Needs a Stripe account that can take payments (get_commerce_setup, create_stripe_connect_link) and editor role.