Requests you created. Open a row for the payment link, QR code and delivery status.

Payment requests created by connected software — one queue, regardless of who initiated them.

Every payment request in the portal, whoever created it.

Every email, text and page a customer can receive from this portal. Pick one and edit its wording; the preview updates live with sample data. Nothing here sends or charges anything.

The purposes staff pick on every request, what each one asks them to confirm, and which ways to pay and card brands its customers are offered. Card is always offered. Bank-verified purposes run the bank's 3-D Secure check on every card and only offer methods that carry a liability shift (plus bank transfer, which stays Processing until it settles). Click a purpose to edit it.

Every user must acknowledge this before a request is sent (or cancel). Staff-facing — customers never see it. Plain text; bullets with • read well.

How long links stay payable, how long bank transfers are held, and who sees app-created requests.

Stores tag every payment for per-store reporting; all stores settle under the company merchant account unless a store is given its OWN complete Cybersource credentials (MID + key ID + shared secret — all three or none). Once any store is active, staff must pick the store on every request. Retire a store by unchecking Active — history keeps its attribution.