SwiftPay Merchant Support

Store owners and authorized employees may call, text, or WhatsApp SwiftPay Support for help using the software. Cardholders must contact the issuing merchant for balances and redemption questions.

Call 470-886-0066 Text Support WhatsApp Support

Before calling about a balance or transaction

Stop card activity if the balance or transaction cannot be verified.
Do not clear browser data or reinstall SwiftPay.
Record the app version, Install ID, device/browser, action attempted, and exact error.
Preserve the device and latest backup.

Activation and renewal help

The store starts its trial by verifying its business email directly in SwiftPay. For paid service, provide the displayed Install ID. Initial paid service uses a one-time ACT-XXXXX-XXXXX-XXXXX code. Each yearly renewal uses a new one-time REN-XXXXX-XXXXX-XXXXX code for the same Install ID. An internet connection is required for trial verification, activation, renewal, and periodic license verification.

Trial records

Trial cards and transactions are test-only and have no monetary value. Paid activation starts a clean production ledger. Trial records remain permanently quarantined and cannot be converted into valid production cards. Support must not instruct a store to recreate trial balances in the production ledger.

Privacy

SwiftPay cannot remotely see the local card database. Licensing requests do not contain card numbers, balances, transactions, users, reports, or backup files. Share screenshots or backup files only through a support method you trust; backups contain sensitive store records.

Store device security

Use SwiftPay only in a store-controlled browser or kiosk profile. Do not allow guest browsing, unapproved extensions, developer tools, or unauthorized operating-system access. SwiftPay signs out after a reload, but a person who administers the device or browser can still access locally stored browser records.

Owner recovery

Owner recovery requires a signed, installation-specific authorization. Used recovery authorizations are rejected. SwiftPay’s private signing keys are never included in the customer build.