Sync processing accounts and activate the profile

A Processing Account is a merchant account at Payload — the account that receives your payments and sends your payouts. You never create one by hand. The Sync Processing Accounts button on the Pay Profile asks Payload for the accounts under your API key and creates a Processing Account record for each. The same sync fills the profile's Profile Id, which is the last thing the profile needs before it can be activated.

Step 1 — Run the sync

1. Open the REDA Pay app → Pay Profiles tab → your profile.
2. Click Sync Processing Accounts. The dialog explains: "System will update the existing and create new processing accounts."
3. Click Sync.
4. Wait for "Processing accounts are synced successfully." and close the dialog.
5. Open the Processing Accounts tab on the profile (or the Processing Accounts list). One record per Payload merchant account is listed, named as Payload names it, with its Status at Payload.

The Sync Processing Accounts dialog on a Pay Profile, showing the note "System will update the existing and create new processing accounts." with the Sync and Close buttons

The sync dialog. Pressing Sync reads your merchant accounts from Payload and creates or updates one Processing Account for each.

The Processing Accounts related list on the Pay Profile after a sync, listing Meridian Operating Account and Meridian Fee Account with Is Active and Status columns

After the sync, each merchant account at Payload has a Processing Account record. The rest of their configuration is yours to do.

What the sync creates, and what it overwrites

On the profile itself, the sync fills Profile Id (encrypted) and Last Sync Datetime [Payload].

Run the sync again whenever Payload adds a merchant account to your organisation, or after you replace the API key. Existing records are updated in place, so your configuration on them survives — except the name, as noted above.

Step 2 — Activate the profile

1. On the Pay Profile, click Edit.
2. Tick Is Active and Save.

If the profile still lacks its API token or Profile Id, the save is refused with "Please provide API Key and Profile Id prior activating the profile." — go back to the previous step that is missing.

Only active profiles are offered on payment screens, and payment screens show only the active profiles the user may see, so activating is what makes the profile usable.

Step 3 — Choose a default processing account

When a profile has more than one processing account that allows the kind of payment being made, staff are asked to choose one under "Select Processing Account" every time. To avoid that:

1. First configure the accounts (at least Is Active, Allowed Transfer Type and Allowed Pay Methods) as described in Configure a processing account.
2. On the Pay Profile, click Edit, choose the main account in Default Processing Account, and Save. The account must belong to this profile.

A Pay Customer can also carry its own Default Processing Account, which applies to that customer's orders.

Worked example: Meridian Properties

Meridian Properties has two merchant accounts at Payload: an operating account where rent and deposits land, and a second account where convenience fees are collected. After the sync, two Processing Accounts appear. The administrator:

1. Opens the first, ticks Is Active, sets Allowed Transfer Type to Receipt and Disbursement, Allowed Pay Methods to Card and Bank Account (ACH), and Interface Label to Meridian Properties.
2. Opens the second, ticks Is Active, allows receipts only, and leaves it for fee routing.
3. Activates the Pay Profile and sets the operating account as its Default Processing Account.

From then on, a staff member opening the payment screen on a Lead goes straight to the operating account.

Mistakes to avoid

FAQ

Where to go next

• Configure a processing account — transfer types, methods, currency, sessions, links.
• Set up webhooks — let Payload report status changes to Salesforce.