Card on File Testing Scenarios

Follow

We've been working on implementing some updates to our Card on File process that are designed to enhance how Recurly stores customer card data for use outside of an active checkout session. For more info on Card on File, check out our Product Docs or our FAQ.

While the majority of checkout flows won't require any updates, we do have some suggested flows you can test in your development site to ensure your Recurly.js checkout won't be impacted by any of the updates.

3DS

Test in the sandbox / development environment through flows your customer will route through naturally. If you use 3DS or a Mobile Wallet ensure you’re testing with test cards/device test data from your respective gateway that supports triggering challenges or consumer authentication. If you’re using Braintree, you may wish to utilize our newly available Proactive 3DS, specifically as it pertains to obtaining 3DS authentication prior to the transaction request.

• 3DS Recurly.js Documentation

Apple Pay and Google Pay

Apple and Google Pay will also require Recurly.js to re-authenticate a return customer. Merchants should test using all payment methods they currently support. Sending a billing info ID or account code for Apple / Google Pay customers for a CIT transaction will not process properly without Recurly.js interaction.

• Apple Pay Recurly.js Documentation
• Google Pay Recurly.js Documentation

Flows to Test

• New Customer sign ups: Brand new customers signing up for a subscription
• Returning Customer sign ups: Return customers signing up for a subscription including:
  • Sign up after cancellation
  • Multi-subscription support using stored billing details
• Updating billing information: Customers changing their billing information for their existing subscriptions.
  • Updating between billing cycles or during dunning
  • Updating billing information while making a one-time purchase or signing up for a new subscription.
• One-time purchases: New or return customers making a one-time purchase.
  • This would likely happen via the Purchase endpoint, and can use an R.js token, an Account ID, a Billing Info ID, raw card details or a gateway token.
• 3D Secure (3DS): If your business supports 3DS, also test any scenarios where 3DS authentication would be expected.
  • Note for merchants using Braintree or Cybersource: You may want to take advantage of our newly available Proactive 3DS (Braintree only), which allows you to obtain 3DS authentication before submitting the transaction request. This helps ensure that verifications go through 3DS authentication successfully and meet EU/UK SCA requirements. For qualifying* Cybersource merchants, please reach out to have a flag enabled on your account.
• Add a Subscription via Recurly Admin: Merchants adding subscriptions for existing customers.
  • Note: EU/UK merchants are advised that this is not recommended due to SCA compliance, and could result in failed renewals.

For any questions you have along the way or if any issues arise, please feel free to open a ticket with our Global Support team for additional guidance.

* Only Cybersource merchants who are using a processor that supports the challengeCode parameter may use proactive 3DS.