Payment Portal
Payment Requests by Email & Text
Request a Payment
$
← Choose at least one
Request Created
The payment link, QR code, and live status are under My Requests.
My Payment Requests
App Requests payment requests created by connected software — one queue, regardless of who initiated them
All transactions
Customer Communications
Every email, text and page a customer can receive from this portal. Pick one, edit its wording, and the preview re-renders live with sample data — exactly what the customer gets. Click a chip to insert a placeholder at the cursor (hover a chip for what it fills in). Nothing here sends or charges anything.
Loading…
Payment Methods by Purpose
Which payment options a customer may be offered for each purpose. Card is always offered: bill-pay purposes charge cards directly, retail purposes run the bank's 3-D Secure verification. High-risk retail purposes only allow methods that carry a liability shift (plus bank transfer, which stays Processing until it settles) — the rest are locked off.
Policy Acknowledgement
Every user must acknowledge this before a request is sent (or cancel). Staff-facing — customers never see it. Plain text; bullets with • read well.
Portal Settings
How long links stay payable, how long bank transfers are held, and who sees app-created requests.
1–365
How long a newly sent payment link stays payable. After that the customer sees an expired-link page and needs a fresh request. Applies to links sent from now on; links already out keep the window they were sent with.
Who sees the App Requests queue — payment requests created by connected software (the AR dashboard today). Emails, separated by commas or new lines. Administrators always see it.
Stores & Merchant IDs
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.
Store Revenue one merchant account, split by store
Collected = PAID (cards captured; ACH settled). Processing = submitted but not final. Every transaction carries its store in the Cybersource merchant reference and report data, so these numbers reconcile against Cybersource settlement reports batch by batch.
Settlement Batches what Cybersource sent to the bank
Activity Log
Payment Portal
Sign in with your ListenUp account
Company Policy Acknowledgment
Re-select what you are sending, then confirm each compliance statement.
Re-select the purpose above to unlock the compliance checklist for this payment.