Issuing カードリスト
発行済みのすべてのカードの一覧を表示します。
Issuing カードリストは、連結アカウントに対して発行されたすべての cards (カード) のテーブルビューを表示します。
The permission boundary for this component is at the connected account level, not at the individual card level. This UI should be shown to users that have access to all cards, not to users that have restricted access to a single card.
アカウントセッションを作成する際に、components
パラメーターで issuing_
を指定して、Issuing カードリストコンポーネントを有効にします。Issuing カードリストコンポーネントの個々の機能は issuing_
で features
パラメーターを指定することで、有効または無効を設定できます。
アカウントセッションを作成して ConnectJS を初期化すると、フロントエンドに Issuing カードリストコンポーネントを表示できます。
Disable Stripe user authentication
disable_stripe_user_authentication 機能を使用して、コンポーネントで Stripe ユーザー認証が必要かどうかを制御します。デフォルトでは、このパラメーターは false です。この値は、controller.
が application
であるアカウントに対してのみ true になります。
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.
支出管理を設定する
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.
機密データの表示
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: