Admin → Financing uses the Banknote icon and stores provider configuration per register. Financing is a sensitive credit/lease workflow. Provider approval, disclosures, pricing, adverse-action handling, eligibility, delivery evidence, settlement, and funding remain governed by the provider and applicable law. The current form has no credential test, delete/reset control, confirmation for location-wide copy, or transactional rollback. It also loads the PayTomorrow API signature from the normal settings payload into browser state when saved, so treat this page as credential-bearing and never capture or share it.
Step by step
- Go to Admin → Financing, identified by the Banknote icon. Confirm the signed-in business and obtain written authorization for the exact PayTomorrow or Katapult merchant account before opening or editing credentials.
- Read the Location and Register selectors immediately. The page automatically chooses the first location returned by name and then the first register returned for that location; it does not intentionally follow the operating-context register. Select the exact target manually before trusting any displayed provider state.
- Changing Location clears the register choice and automatically selects the first register in the new location when available. The provider tabs appear only after a register is selected. If no register appears, configure/authorize the location’s register rather than assuming the provider is disabled.
- Choose PayTomorrow or Katapult. Each tab loads only the selected register’s stored rows and initializes a draft. Switching register/provider replaces the draft; save deliberate changes before switching and never paste one merchant’s values into another tenant or register.
- Interpret Connected cautiously. PayTomorrow shows Connected when a saved API Username exists. Katapult shows Connected when a saved Merchant ID exists. This does not validate the password/key, API signature, public token, environment, merchant ownership, account status, callback, provider availability, or successful application flow.
- The Enabled switch changes only the current draft until Save. Turning it off does not remove credentials or historical applications. Turning it on does not prove provider readiness, customer qualification, legal approval, channel eligibility, or that the payment choice will appear in every cart.
- For PayTomorrow, enter the provider-issued API Signature used for the OAuth Basic authorization header, API Username, API Password, and optional Merchant Reference ID. Confirm the exact production/test account and required scopes directly with the provider.
- Treat the PayTomorrow API Signature as fully sensitive. Although password-masked, a saved signature is read from the settings payload into this browser and can be revealed with the eye control. The page’s generic credential-encryption wording must not be relied on for that field. Do not use Show on a shared screen, remote session, recording, or screenshot.
- A saved PayTomorrow API Password is represented by a masked placeholder and is not populated into the draft. Leaving the password field blank on a later save preserves the stored encrypted column because the field is omitted from the update. The current form provides no explicit clear/delete credential action.
- For Katapult, enter the provider-issued API Key, Merchant ID, and Public Token used by its checkout widget. The saved API Key is represented by a masked placeholder and is not loaded into the draft; leaving it blank on a later save preserves the stored key. Merchant ID and Public Token do load into ordinary browser fields.
- Use the eye control only to review a newly typed PayTomorrow signature/password or Katapult API key in a private environment. The shared secret-visibility state is reused within each provider form; hide the value immediately and clear clipboard/history under the business’s credential policy.
- Set Minimum Cart Value as a whole numeric currency threshold at or above zero. The input has min 0 and step 1, but the draft uses JavaScript numeric conversion and the form has no explicit finite/range/currency validation or maximum. Enter only a reviewed nonnegative amount and test boundary/rounding behavior.
- Choose Production only for approved live credentials and transactions. Choose Staging only for a provider-supported test account. The selector stores the label but does not test that the credentials belong to that environment; mismatching them can fail or route to the wrong provider system.
- For the selected register, choose Save PayTomorrow Settings or Save Katapult Settings once. The save upserts the provider row for the current tenant/register/provider. Wait for Financing settings saved, then reselect/reopen the same register and verify Enabled, environment, threshold, username/merchant/public-token evidence, and masked secret placeholder.
- Understand credential updates. A newly entered PayTomorrow password or Katapult key is written to its corresponding encrypted-named database column; a blank draft omits that field and preserves the prior value. The UI does not prove encryption-at-rest implementation, rotate a credential, revoke the old provider credential, or let you intentionally clear it. Verify those requirements with the authorized platform/provider owner.
- Apply to location appears only on the Katapult tab and only when the selected location has more than one register. PayTomorrow has no location-wide copy action. For Katapult, the action targets every other loaded register ID at the selected location; it does not resave the currently selected register. Save the current register first when its draft must also persist.
- Before Apply to location, confirm every target register, merchant account, environment, Enabled state, threshold, Merchant ID, Public Token, and API Key policy. There is no confirmation dialog. The operation launches one upsert per other register concurrently and is not all-or-nothing; one failure can leave a partial location rollout.
- If the Katapult API Key field is blank during Apply to location, the request omits the key update for each target, so an existing target key can remain rather than inheriting the selected register’s stored key. The function cannot read/copy the stored selected-register key from its masked placeholder. To intentionally align keys, enter the approved key during the controlled operation or use an authorized backend process, then verify every target separately.
- Wait for Katapult settings applied to all registers at this location or the failure message. In either case, open each register individually and inspect its Katapult state. A success toast proves the submitted upserts returned without error; it does not prove provider authentication. A failure requires a per-register audit before retrying because earlier concurrent writes may have succeeded.
- Run a controlled register matrix without using a real applicant: selected versus other register; Enabled/disabled; below, exactly at, and above the minimum; staging versus production test context; PayTomorrow versus Katapult; eligible sale channel; attached demo customer; and cancellation before external submission. Confirm only intended options appear.
- When authorized to test a real provider sandbox flow, use a designated provider-approved demo identity. Verify branded handoff, merchant/environment, requested amount, provider application ID, return/callback, CentriPOS receipt/application linkage, and no duplicate. Do not submit a credit or lease application for an uninformed real person.
- After launch, use Admin → Financing Apps for provider status, delivery/pickup evidence, PayTomorrow settlement, and funding lifecycle. Financing setup does not advance an application or prove funding. Reconcile provider records and rotate credentials under an approved process when staff, scope, or exposure changes.
- No screenshot is published for this guide. The real Amelia Grant Harbor & Hearth page contains API signature, username, password, merchant reference, environment, and register-specific provider configuration, so the capture was rejected as credential-sensitive rather than redacted, invented, or replaced.
Screen and contract reference
| Control or area | What it means |
|---|---|
| Banknote icon | Exact CentriPOS Admin navigation and page icon for Financing. |
| Location selector | Automatically starts at the first returned location by name; manually verify the intended scope. |
| Register selector | Automatically starts at the first returned register for the selected location; provider settings are stored per register. |
| PayTomorrow / Katapult | Independent provider tabs for the exact selected register. |
| Connected | Field-presence indicator only: PayTomorrow API Username or Katapult Merchant ID exists. |
| Enabled | Draft availability flag saved with the provider row; not a connection or approval test. |
| PayTomorrow API Signature | Sensitive OAuth Basic-header value stored in the normal settings payload and loaded into browser state. |
| API Username | PayTomorrow credential identity used as the Connected indicator. |
| API Password | Sensitive PayTomorrow value; saved value is not repopulated and blank later saves preserve it. |
| Merchant Reference ID | Optional PayTomorrow merchant reference in the merchant_id field. |
| Katapult API Key | Sensitive value; saved value is not repopulated and blank later saves preserve it. |
| Katapult Merchant ID | Required operational merchant identifier and Katapult Connected indicator. |
| Public Token | Katapult checkout-widget token stored in the provider row and loaded into the browser field. |
| Eye control | Reveals the newly entered secret or loaded PayTomorrow signature; use only in private. |
| Minimum Cart Value | Whole-step numeric draft with no explicit finite/maximum/business-rule validation. |
| Production / Staging | Stored environment selector; it does not validate credential/environment compatibility. |
| Save provider settings | Upserts the selected tenant/register/provider only. |
| Encrypted-named columns | Password/key destinations by schema name; the page itself does not prove encryption implementation or rotation. |
| Apply to location | Katapult-only, no-confirmation concurrent upsert to every other register at the selected location. |
| Selected-register exclusion | Apply to location does not save the currently selected register. |
| Blank Katapult key during copy | Omits key changes and can leave each target’s existing key intact. |
| Partial rollout risk | Concurrent target writes are not transactional; inspect every register after success or failure. |
| Financing Apps | Separate lifecycle page for applications, delivery/pickup, settlement, and funding. |
| No public screenshot | The approved real Harbor & Hearth financing page was rejected because it contains credential-bearing fields and provider/register configuration. |
Expected result
Only the intended provider appears on the exact register at the reviewed environment and cart threshold; credential ownership and provider authentication are independently verified, no secret is exposed, any Katapult location copy is audited register by register for partial or preserved-key differences, and a controlled provider-approved demo flow follows the correct merchant without creating a real customer obligation.
Troubleshooting
- Confirm you are changing the intended business and location before saving.
- Record the previous setting when a change affects live selling, payments, tax, or integrations.
- Use a controlled test record after saving before rolling the setting out broadly.
CentriPOS API explorer · API Center administration