Skip to main content
Vaultera Switch supports multiple ways to save a customer’s payment method, especially useful for recurring or future payments:
  • On-session payments (COF-CIT)
  • Off-session payments (MIT)

✅ Save for Future On-Session Payments (COF-CIT)

This is used when the customer is present during the transaction and can authenticate the payment (e.g., enter CVV or perform 3DS). This is common in card-on-file, customer-initiated transactions.

➤ How to Save:

  1. Include in /payments create request:
  1. Include customer consent in /payments/:id/confirm request:
  1. If using Vaultera Switch SDK:
    • Consent is sent automatically based on the “Save Card” checkbox.
    • Enable via displaySavedPaymentMethodsCheckbox property.

💾 Save for Future Off-Session Payments (MIT)

This is used when the customer is not present (off-session) during payment. Common in subscription or invoice scenarios.

➤ How to Save:

  1. Include in /payments create request:
  1. Include customer consent in /payments/:id/confirm:
  1. Retrieve and store the payment_method_id:

💸 Use a Saved Payment Method for MIT

To charge a customer later using a previously saved payment method:

➤ In /payments create request:

Use the payment_method_id retrieved from the previous successful save.

📋 List Saved Payment Methods


🔓 Process MIT Payments Without Saving

If you’re PCI-compliant and already have the customer’s card details:

➤ Use the card + network transaction ID:

➤ Use routing with supported connectors:

Currently supported by Stripe, Adyen, and Cybersource. For additional connector support, submit a feature request.

❓ FAQ

Q: How can I vault a payment method without charging the customer?

You can use Zero Amount Authorization to authenticate and store a card without charging it. Ideal for onboarding flows.
🔗 Refer to Zero Amount Authorization for implementation details.