Loading article…
Loading article…
Last updated on Aug 28, 2026
Before you can test and implement 3D Secure, you need to know every access point where your customers enter a credit card that Advanced Billing processes. An access point is anywhere your end-customer may enter a credit card that is used by Advanced Billing.
Important: If you are unsure which method is being used, contact support@maxio.com; the support team can help you find how your customers are signing up or updating their cards. The development or IT team that worked on your integration has the most knowledge on which access points your company uses.
Please be aware that this article is related to testing and implementing 3D Secure. We currently support 3DS on the following gateways: Stripe, Braintree, CyberSource, Windcave (Payment Express), Adyen.
Maxio.js allows you to collect card information using embedded iframes on your own site (see Maxio.js Overview). One way of helping you determine if this is being used is by seeing if you have a Public Key generated under Config > Integrations > Maxio.js.
Additionally, if your signup or card update page on your own customer-facing site embeds the Maxio.js file, this could indicate that this access point is being used.
Advanced Billing's API can be used to create and manage Subscriptions. Check whether you have an API key generated under Config > Integrations > API Keys/Chargify Direct.
Bear in mind that API keys generated here may be used not to directly interact with our API, but rather to communicate with a third-party application, such as Salesforce. If you are directly integrated with our API to process signups, there is code on your server that references this API key, and it is likely that you are not using our Public Signup Pages.
These are Advanced Billing-hosted pages that are used to create Subscriptions. Public Signup Pages allow the customer to fully configure their Subscription with products, components, and coupons (see Understand Public Signup Page Details); Offer Signup Pages are a static signup form that can be sent as an already-configured deal for a particular customer (see Create and Manage Offer Signup Pages). You can determine if you have any enabled Public Signup or Offer Signup Pages by going to Billing > Public Signup Pages or Billing > Offer Signup Pages. That said, the existence of these pages does not necessarily mean they are being used to sign up your end customers; the only way to know for certain is to determine if these links are embedded in your website.
Another way of determining if they are being used is if your customers are directed to a chargifypay.com domain name as part of the signup process. The URL resembles the following: https://subdomain.chargifypay.com/subscribe/w3k4sc2jqydk
Understand Self-Service Pages are Advanced Billing-hosted pages used to update credit card information. If you have emails enabled in Advanced Billing, such as signup or renewal emails, they reference an update_url variable, which pulls in each subscriber's unique service link. Additionally, if your team manually sends payment update request emails from a Subscription's Payment Details tab using Email Customer to Request Payment Update, these emails reference Self-Service Pages by default.
Self-Service Page URLs are hosted on the chargifypay domain and contain the Subscription ID and your Advanced Billing site's subdomain. An example URL is formatted as follows: https://<subdomain>.chargifypay.com/update_payment/<subscription_id>/f1078bae2f
The Billing Portal allows customers to self-manage their Subscriptions (see Understand the Billing Portal); in particular, if the feature is enabled, they can be used to update the credit card on file.
You can determine if your Billing Portal workflow is affected by PSD2 by first checking whether the portal is enabled under Config > Settings > Billing Portal. If Billing Portal is enabled, check whether Allow Card Updates is enabled under the Billing & Payments section.
This refers to the public views that customers can use to pay off their open or past due invoices. Steps for verifying whether these URLs are used vary based on the site's architecture. See below for the section that applies to you.
Click on the Billing navigation in your site. If it lists Transactions and not Payments, your site may be using statement-based invoices. This is referred to as invoice billing and is not enabled by default.
Visit Config > Settings > Invoice Billing to determine whether the feature is turned on, and whether Enable Pay by Credit Card Link In Invoice is turned on.
Click on the Billing navigation in your site. If it lists Payments and not Transactions, your site is on Relationship Invoicing (see Understand How Invoices are Generated).
Check whether you have invoice emails turned on, particularly for remittance payments, with invoice.url defined in the email template. If you export Subscriptions, check whether any have a payment_collection_method of "remittance." It's possible that a member of your team may be manually sending the public URL to customers as needed.
For an overview of testing and implementing 3D Secure, see Test and Implement 3D Secure.
Still need help?
Reach out and our support team will take it from here.