What Is Changing with Payment Methods in Keap

Keap is transitioning from storing client credit card data in raw format to storing it in a fully tokenized format. A token is an encrypted string of characters that represents a payment method. Tokens are generated by the payment processor at the time of the transaction and can only be used by the processor that created them. The raw card number, expiration date, and other card details are never stored in Keap after tokenization is complete.

The most significant practical change is that a card tokenized for one processor cannot be charged through a different processor. Previously, if a client entered their card through Processor A, you could later charge that same card through Processor B without requiring the client to re-enter their card number. After the transition to tokenized payment methods, you can only charge a card through the processor it was originally entered with.

What Tokenized Payment Methods Are

Tokenization converts raw payment information into a processor-specific token at the moment a card is entered. When a transaction occurs, only the token is transmitted between Keap and the payment processor — the actual card number, expiration date, and other card details are not sent or exposed during the transaction. This applies to all processors including Keap Pay.

Because each token is specific to the processor that created it, a card tokenized for Processor A has a different token than the same card tokenized for Processor B. If you want to charge the same card through a different processor, the client must re-enter their card information through that processor to generate a new token for it.

What Is Changing in the App

Payment Input Fields

The fields your clients use to enter their card details will begin to look different depending on which payment processor is handling the transaction. This is expected behavior — the card entry fields are now owned and rendered directly by each processor rather than by Keap. The appearance of these fields may vary by processor.

Credit Cards on File Renamed to Payment Methods

The section previously labeled Credit Cards on a contact record is being renamed to Payment Methods. This rename reflects the broader range of payment types the section will support going forward, including ACH and Apple Pay.

The display format for saved payment methods is also being updated. Currently, each saved card is shown by its last four digits. After the transition, the display will include the processor the card is tokenized for in parentheses after the last four digits — for example: Visa ending 4242 (Keap Pay). If the same card has been entered through multiple processors, each processor-specific token will appear as a separate entry in the Payment Methods list. This makes it easy to see which processors are available for a given card without needing to open each entry.

Adding a New Payment Method

Before adding a new payment method to a contact record, you will now need to select which processor you want to tokenize the card with. You can add the same card for multiple processors by repeating the process and selecting a different processor each time. Each processor-specific entry will appear separately in the Payment Methods list.

Subscriptions, Recurring Payments, and Payment Plans

Any subscriptions, recurring payments, payment plans, or Action Sets currently set to use the default processor will automatically be locked to a token for whichever processor is set as the default at the time the transition occurs for your account. After the transition, the concept of a default processor for subsequent charges no longer applies — each recurring charge is tied to a specific processor token rather than a default setting.

If you want to change which processor handles an existing subscription or recurring payment after the transition, update the payment method on that order or invoice to the token for the desired processor.

Example: If you have a monthly subscription for a client and you are connected to Keap Pay, Stripe, and PayPal with Stripe set as the default processor, the subscription will automatically be locked to the Stripe token when the transition occurs. To move the subscription to Keap Pay or PayPal, update the payment method on that subscription to the Keap Pay or PayPal token for that client's card.

If you are switching to Keap Pay, all existing subscriptions and recurring payments can be moved to Keap Pay tokens as part of the upgrade process.

API-Driven Payment Calls

After the transition, the Keap API will no longer accept raw credit card data from third-party systems. Any API call that attempts to send raw card information to Keap will fail and be rejected. If a payment method has already been tokenized and stored in Keap, that token can still be used to initiate a transaction via the API — you will use the token API instead of the card number API.

Sending card updates to Keap via API is also no longer supported after the transition. Card updates must be entered through the processor-specific payment input fields in the app. Third-party companies that use the Keap API for payment-related calls are adjusting their integrations. Monitor updates from any third-party tools you use for payment processing to understand when and how their integrations will change.

How Keap Is Protecting Your Existing Payment Methods During the Transition

All Existing Cards Are Being Tokenized for Every Connected Processor

To ensure no interruption to your ability to charge clients, every credit card currently on file in your Keap account will be tokenized for every payment processor you have connected at the time of the transition. This means you will see more entries in each contact's Payment Methods list — one entry per card per processor.

Example: If a contact has two cards on file and you are connected to Keap Pay, Stripe, and PayPal, you will go from seeing two payment options for that contact to six — one entry for each card for each of the three processors.

Subscriptions and Recurring Payments Will Be Automatically Updated

Any subscription, recurring payment, or payment plan currently set to run against your default processor will automatically be updated to use the token for that default processor when the transition occurs for your account. No manual action is required to keep recurring charges running. If you want to change which processor handles a recurring charge after the transition, update the payment method on that order or invoice to the desired processor's token.

Rollout Timeline

The transition to tokenized payment methods is being rolled out in three phases.

• Phase 1 — Began March 4, 2024. Any new customer who signs up to use Keap Pay is automatically transitioned to token-only storage at signup.
• Phase 2 — Date to be announced. When Stripe Elements is re-released, all accounts with an active Stripe connection will automatically be transitioned to token-only storage.
• Phase 3 — Date to be announced. All remaining accounts not yet transitioned will automatically switch to token-only storage.