Once you've integrated Stripe with FieldCamp, you can store multiple payment cards directly in your client profiles. This feature enables seamless payment collection and streamlines your billing workflow by allowing clients to have several payment methods on file.
How Payment Cards Are Stored and Protected
When you add payment cards to a client profile in FieldCamp, the card data is securely stored in your Stripe account, not in FieldCamp. This architecture ensures PCI (Payment Card Industry) compliance and maintains the highest security standards for sensitive payment information.
Key Security Points:
FieldCamp does not store any card data directly
All card information is encrypted and stored securely by Stripe
You'll only see the last four digits of each card in the FieldCamp interface, ensuring sensitive information remains protected
The full card data remains accessible to Stripe for payment processing without exposing it in your FieldCamp workspace
Adding Payment Cards to a Client Profile
To add a payment card to a client profile:
Open the client profile where you want to store the card
Navigate to the payment methods or cards section
Click Add Card or Add Payment Method
Enter the card details (card number, expiration date, CVV, and cardholder name)
The card information is securely transmitted to Stripe for storage
Once added, the card will appear in the client's profile showing only the last four digits
You can add as many cards as needed per client profile, giving you flexibility in managing multiple payment methods for a single client.
Managing Stored Cards
Viewing Your Cards
Once cards are added to a client profile, you'll see them listed with:
Card type (Visa, Mastercard, American Express, etc.)
Last four digits of the card number
Expiration date
A designation indicating which card is the default payment method
This limited display protects sensitive information while keeping you informed about which cards are available for payment collection.
Setting a Default Card
You can designate one card as the default payment method for a client. The default card will be used automatically when:
Collecting payments for invoices
Processing auto-deducted payments for recurring jobs with the auto-invoice feature enabled
To set a default card:
Go to the client profile's payment methods section
Select the card you want to make default
Click Set as Default or a similar option
The card will now be marked as the primary payment method for automatic payment processing
You can change the default card at any time by selecting a different card and updating the designation.
Deleting Cards
Clients can remove payment cards from their profile at any time. To delete a card:
Navigate to the client profile's payment methods section
Locate the card you want to remove
Click the Delete or Remove button next to the card
Confirm the deletion when prompted
The card will be removed from the client profile
Once deleted, the card can no longer be used for future payments. If the deleted card was set as the default, you'll need to select a different card as the new default.
Updating Cards
Important: Cards cannot be edited or updated directly in FieldCamp. If a client needs to change card details (such as updating an expiration date), they must:
Delete the existing card from their profile
Add a new card with the updated information
This approach maintains security by ensuring that all card information goes through Stripe's secure channels rather than being modified within FieldCamp.
When Payment Cards Are Used
Payment cards stored in client profiles are used during:
Manual invoice payment collection – When collecting payment for individual invoices
Auto-deducted recurring payments – When recurring jobs have auto-invoicing enabled, FieldCamp can automatically deduct payments from the default card (see our article on auto-invoicing and auto-payment for more details)
Best Practices
Regularly review stored cards – Periodically check client profiles to ensure only current, active cards are stored
Keep a default card updated – Make sure the default card is valid and current to prevent payment failures
Communicate with clients – Let clients know they can manage their own cards in their profiles, reducing support requests
Monitor expiration dates – Keep an eye on card expiration dates, especially for recurring payments
Document card changes – If a client updates their card information, note the change for your records
FAQ
Q: Can I see the full card number in FieldCamp?
A: No. For security and PCI compliance reasons, FieldCamp only displays the last four digits of each card. The full card information is securely stored by Stripe.
Q: Who can manage payment cards in a client profile?
A: Clients can add and delete their own cards. However, specific permissions may vary based on your FieldCamp workspace settings—check with your administrator for details.
Q: What happens if the default card expires?
A: If the default card expires, automatic payments will fail. You'll receive a payment failure notification, and the client will be notified of the declined card. Update the default card to a valid method to resume automatic payments.
Q: Can I add cards on behalf of a client?
A: This depends on your workspace permissions. Some setups allow team members to add cards for clients, while others restrict this to the client themselves. Check your admin settings for more information.
Q: Is there a limit to how many cards I can add per client?
A: There is no hard limit on the number of payment cards per client, though storing too many may create confusion. We recommend keeping 2-3 active cards per client.
Q: Are my cards safe with Stripe?
A: Yes. Stripe is PCI DSS Level 1 compliant, the highest level of security certification. All card data is encrypted and protected to industry standards.