Set up the public payment-link site

A payment link opens a page that anyone can reach without logging in. In Salesforce that is a public Experience Cloud site — or public pages in an existing site — whose guest user is allowed to run the REDA Pay screens and to read exactly the order behind the link, nothing else. This article builds that site, grants the guest user what it needs, and connects it to your processing account.

Part 1 — The site and its pages

1. Setup → Digital Experiences → All Sites → New (if you are creating a site). Choose a template such as Build Your Own, name it, give it a path such as pay, and create it. Or open your existing public site.
2. In Experience Builder, create four pages, as in the portal set-up, but on a site or pages that guests can see:

1. If vendors will enter bank details through a link (see Request bank details from a vendor), add the same set with NewPayMethod (and Portal Method Input Page), NewPayMethodRequest and NewPayMethodResult.
2. Make the pages public: in each page's properties, set page access to Public, and under Settings → General → Public Access select Guest users can see and interact with the site without logging in.
3. Publish.

Write down the full address of the link entry page, for example https://yourcompany.my.site.com/pay/s/process-order-link.

The entry page carries the whole configuration; the request page just renders the screen.

Part 2 — The guest user

Every public site has a guest user and a guest profile; an anonymous payer is that user while on your page. Give it the REDA Pay access: assign REDA Pay - Public Site User to the guest user, or put the same settings on the guest profile. It grants read on Pay Orders, Pay Customers, Pay Profiles, Processing Accounts and Fee Setups, create on Pay Methods and Pay Transactions, the Apex classes behind the screens, and read access to the REDA Pay Process Config and REDA Pay Setup custom metadata types. Each step, with the alternatives, is in Payment-link guest access: permissions and sharing.

Part 3 — Guest sharing rules

A permission set says what kind of record the guest may read; sharing rules say which records. The guest must see an order only while its link is active, and a customer only while they have a live link. Create these under Setup → Sharing Settings, choosing Guest user access, based on criteria and the site's guest user as the target, all Read Only:

REDA Pay turns Has Active Link off when the order is paid or revoked, and about a minute after the link expires, so the order disappears from the guest's view by itself.

The Pay Order sharing rules list in Setup showing a guest-user criteria rule "Has Active Link equals True" for the public site's guest user with Read Only access

The guest sees an order only while its link is active.

Part 4 — Connect the processing account

On each Processing Account that will issue links:

1. Link Site Public URL: the full address of the link entry page from Part 1.
2. Link Expiration (Minutes): how long links live, counted from creation. Fill it in — a link created while it is blank never activates.
3. Optionally Payment Session Duration (Minutes) for guests, and Enforce Geolocation for Link and Guest if you want payers' locations recorded.

See Configure a processing account.

Part 5 — Test

1. Create a test link for a demo customer: Create and send a payment link.
2. Open Link URL in a private browser window. The branded payment screen appears with the amount locked and the notes shown. Try it at phone width too.
3. Cancel without paying, then revoke the test order.
4. Open the same address with a character removed: "Invalid request: Bad request Parameters." proves that a guest cannot reach anything but a live link.

Mistakes to avoid

FAQ

Where to go next

• Payment-link guest access: permissions and sharing
• Create and send a payment link
• What the customer sees on a payment link
• Payment link troubleshooting