Issuing cards listPrivate Vorschau
Show a table of all issued cards.
Issuing cards list renders a table view of all the cards issued to your connected accounts.
When creating an Account Session, enable the Issuing cards list component by specifying issuing_
in the components
parameter. You can enable or disable individual features of the Issuing cards list component by specifying the features
parameter under issuing_
.
After creating the account session and initializing ConnectJS, you can render the Issuing cards list component in the front end:
Disable Stripe user authentication
Use the disable_stripe_user_authentication feature to control whether the component requires Stripe user authentication. By default, this parameter is false. Only platforms responsible for collecting updated information when requirements are due or change (including Custom accounts) can disable Stripe authentication.
We recommend implementing 2FA or equivalent security measures as a best practice. For account configurations that support this feature, such as Custom accounts, you assume liability for connected accounts if they can’t pay back negative balances.
Set spending controls
You can use Issuing Connect embedded components to view and, optionally, edit spending controls on your cards by turning on the Issuing component’s showSpendControls
attribute.
To enable editing spend controls in the component, pass spend_
as a feature when you create an AccountSession.
Sensitive data display
Issuing Connect embedded components integrate with Issuing Elements to provide a PCI-compliant way for you to allow your admins to view card numbers (PANs) and CVV or CVCs for virtual cards. The sensitive data renders inside Stripe-hosted iframes and never touches your servers.
The components can use an ephemeral key to securely retrieve card information from the Stripe API without publicly exposing your secret keys.
To enable this functionality you must:
- Set up an ephemeral key exchange on your server.
- Pass an asynchronous callback to the components.
Stripe generates a nonce
from the Card ID in the Issuing Card or Issuing Cards List component when a card is selected or loaded. Stripe then calls your callback function which returns an ephemeral key, and then renders a Show numbers
button if the ephemeral key is valid.
Ephemeral key exchange
Your server-side endpoint needs to accept a Card ID and a nonce
. It can then create an ephemeral key using Stripe.
Here’s how you might implement an ephemeral key creation endpoint in web application frameworks across various languages:
Asynchronous callback
You must define an asynchronous function that accepts a named argument with property issuingCard
which is a Card ID and additionally, a nonce
property. This function must return an Object
with properties issuingCard
, nonce
, and ephemeralKeySecret
which are retrieved from the endpoint you set up in the previous step.
Here’s how you might implement this callback:
Request access Private preview
Sign in to request access to this Connect embedded component in preview.
If you don’t have a Stripe account, you can register now.