Upgrading REDA Pay

REDA Pay is a managed package: a new version is installed over the old one with an installation link, and your data, configuration and customisations stay. Upgrades are routine, but three things a managed upgrade never does catch administrators out every time, so this article is as much a checklist as a procedure.

Check what you have

Setup → Installed Packages lists REDA Pay with its Version Number. Release notes on this portal name the version they describe; compare before reading them.

Upgrade a sandbox first

1. Open the installation link while logged in to the sandbox (or choose the sandbox login when the link asks).
2. Choose who gets access to the package's components. Install for Admins Only is the safe default — access is granted by the REDA Pay permission sets, not by the install choice.
3. Click Upgrade and wait for the confirmation email.
4. Run the checks in the next sections, take a test payment against Payload's test environment, and only then repeat in production.

The three things an upgrade never does

A managed upgrade installs new components but does not touch things you may have customised. For every new field or value a release note lists, do these by hand:

1. Place new fields on your page layouts

If you have ever edited a REDA Pay page layout — and most orgs have — a new field is installed but not placed on your layout. Only untouched, package-default layouts receive it. For each new field the release note lists: Setup → Object Manager → the object → Page Layouts → your layout, drag the field into the section the note names, Save.

2. Grant field-level security to your own permission sets and profiles

The package grants new fields to its own permission sets. If your users hold your own permission sets or profiles instead of, or as well as, the REDA Pay ones, they have no access to the new field until you grant it: Setup → Object Manager → the object → Fields & Relationships → the field → Set Field-Level Security, tick Visible (and Read-Only as appropriate) for each profile or permission set.

Test as an ordinary user of the relevant role, never as an administrator — administrators see fields regardless of field-level security, so testing as yourself proves nothing.

3. Add new picklist values by hand

An upgrade never adds a new picklist value to a field your org already has. Fresh installs get it; upgraded orgs do not, even when a new field arrives in the same release. If a release note lists a new value, add it exactly as spelled: Setup → Object Manager → the object → Fields & Relationships → the field → New → the value → Save, then reorder it. On a restricted picklist a missing value makes the feature fail outright, not just hide an option.

Where your version lives. Compare it with the release notes before reading them.

Reading a release note

Each REDA Pay release note on this portal carries, for every change, the steps to do in your org. Read it with the three rules above in mind:

Sandbox test script

Run this in the sandbox after upgrading, as a user who holds only the relevant REDA Pay permission set:

1. Open a Lead and press the Pay button; the screen opens with logo and tabs.
2. Take a $1 bank payment against Payload's test environment; the order shows Immediate - Processed.
3. Open the Pay Transaction and press Sync Transaction; it completes.
4. Create and cancel a schedule; create a link, open it in a private window, revoke it.
5. As a portal user, open the portal payment page and reach the payment screen.
6. As an administrator, open the Pay Profile: Webhook Setup lists ten rows; press Sync Processing Accounts; it succeeds.
7. Check REDA Pay Logs for anything new.

If any step fails in the sandbox, stop and contact support@reda.one with the step and the message before touching production.

Telling your users

An upgrade rarely changes what staff see, but when a release adds a button, a field or a screen, tell the people who use it before they find it. The release note's "what you'll see" section is written to be forwarded.

Things that survive an upgrade, and things to re-check

After the upgrade: a ten-minute check

1. Installed Packages shows the new version.
2. REDA Pay Admin tab: key Generated, recovery job toggle Yes.
3. Take a test payment as a staff user and, if you have them, as a portal user and through a link.
4. Open a Pay Order and a Pay Transaction as a non-administrator: every field the release note added is visible.
5. REDA Pay Logs: no new Attention Needed entries.

Mistakes to avoid

FAQ

Where to go next

• Who can do what: permission sets
• Setup roadmap