Start with the question the employee is asking
“My card did not work” can describe several different failures. Payroll owns questions about hours, net wages and the destination recorded for payment. The card program or issuer handles card activation, account access, card replacement and card transaction issues under its terms. The employer should provide the current official support route for the relevant program. Corpay publishes cardholder contact information; verify that the number matches the employee’s materials before printing it in a local packet.
This site has no access to a card account and cannot troubleshoot a person’s credentials. A clear division prevents HR from requesting card numbers, PINs or one-time codes in an ordinary ticket.
A triage script that preserves privacy
Ask which payday and what wage amount is shown on the pay statement, then compare the employer’s payroll record and delivery status. If the wage instruction was rejected, payroll should use its authorized correction path. If the instruction was accepted and the worker cannot access the card, direct the worker to the provider’s official channel while retaining the payroll case reference. Do not imply that a support referral discharges the employer’s wage obligations.
Keep the two case tracks linked through a limited internal reference rather than sending full employee financial documents to every participant. Restrict access to staff with a real need. Exact privacy and record-retention rules depend on the employer, its vendors and applicable law.
Differentiate access from a dispute
A forgotten password or a replacement card is not the same as an allegedly unauthorized transaction. A disputed transaction may involve time-sensitive rights under the account agreement and federal rules; the worker should use the official issuer/provider instructions promptly. The CFPB publishes electronic transfer compliance guidance but an HR desk should not adjudicate account disputes.
The employee may also ask why the pay statement differs from the deposit. Payroll should investigate the wage calculation and instruction while the provider investigates account activity. Document the chronology without declaring that a particular party is at fault before the records are compared.
Close the loop
A referral is not a resolution. Confirm that the worker knows the next step, record which team owns it and agree when to follow up. If wages were late or unavailable, escalate within the employer process and obtain case-specific advice as needed. Future onboarding material should address patterns that recur, without publishing details of an individual’s account.
For the underlying reconciliation steps, read the payroll handoff guide. For employee-facing documents, read the disclosure packet guide.
When one complaint spans both sides
Consider an employee who says an expected deposit is absent and the app also will not open. The login issue belongs in the account-support channel, but it does not answer whether the employer calculated and delivered the wage. Payroll should examine its own records in parallel, keep the employee informed, and avoid a circular referral between desks. Neither the HR team nor this publication should ask for a password to check the issue.
A question about card fees is another split case. HR should provide the current governing fee documents and the applicable choice policy. A disputed charge or account-specific posting is for the official provider or issuer process. Staff can explain who owns which question without offering a legal determination, speculating about the charge, or posting an employee’s transaction history to a shared ticket.
Write the escalation sheet in ordinary language. Include the employer payroll contact, the verified program support route, who handles a late-wage exception and how the employee is told what happens next. Review numbers and links periodically, especially during the Fintwist to Corpay Prepaid name change. A printed card or old intranet article can outlast the web page from which it was copied.
Practice the boundary with examples
For training, give staff a small table of examples without actual personal data. “My net wages are wrong” routes to payroll calculation; “the payroll destination was rejected” routes to the employer’s pay-delivery procedure; “I forgot my card password” routes to official card support; and “I see a transaction I do not recognize” should reach the account dispute instructions promptly. Staff can always listen and record the question, but should avoid promising an outcome outside their authority. Add a field for the next update to the worker. Ownership becomes clearer when each incident has both an investigation route and a communication route.