When a shift charge fails, ShiftSee notifies you immediately and pauses outbound shift requests with a payment method warning.
Common causes
- Insufficient funds. Most common. Top up the account or switch cards.
- Card expired. Check the expiry date on Payments → Methods.
- CVC mismatch. Re-enter the security code.
- Card frozen by your bank. Banks sometimes flag SaaS charges as suspicious. Call your bank or approve the charge in your banking app.
- Issuer doesn't allow recurring or international charges. Use a different card.
- Stripe risk decline. Rare; usually resolves on retry from a different IP. Contact support if it persists.
Fixing it
- Payments → Methods, add a working card and set it as default.
- Click Retry charge on the failed shift in Payments → Payment History.
- The shift moves back to confirmed. The shifter is paid on the normal timeline.
What happens to in-flight shift requests during a payment problem?
ShiftSee won't auto-cancel in-flight shifts on a card decline; we just block new outbound shift requests until you fix the method. Already-accepted shifts proceed and we retry the charge once the card is updated.