#dennis_docs
1 messages · Page 1 of 1 (latest)
👋 Welcome to your new thread!
⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.
⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.
🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1439005203960434703
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
- dennis_docs, 50 minutes ago, 3 messages
Hi, you'd want to follow this integration, https://docs.stripe.com/payments/save-and-reuse?payment-ui=elements if you're looking to collect the payment method details in a PCI compliance manner. This allows you to reuse the payment method multiple times on the same customer.
Alternatively, if you're charging the customer on the first payment and wanting to save the payment method details for future use, you can use, https://docs.stripe.com/payments/checkout/save-during-payment
So we are currently creating a customer and payment method in Stripe. The guide you linked shows how to charge that card by creating a payment intent- however what we want to do is securely provide the card information to another merchant for them to place a charge against the card.
It looks like providing a network token could do this https://stripe.com/guides/understanding-benefits-of-network-tokens
Are there other types of payment tokens that could do this as well?
Do you mean that you're the payment orchestration provider, which you will send the payment method details to different accounts on Stripe?
Yes, more or less. We don't want to send card details per se, but an identifier (token?) which would allow other accounts to place a charge against the card
The payment method token / identifier is binded to a specific account in Stripe. The tokens can't be shared between accounts
The only possible way is to create an organisation for your accounts and share the payment method IDs between accounts: https://docs.stripe.com/get-started/account/orgs/sharing/customers-payment-methods
Ah I see, thanks! Follow-up question: from the Payment tokenization guide it sounds like network tokens might be a specialized case of general payment tokens.
What other kinds of payment tokens are there, and can you share links to related guides and APIs?
There are only two types of tokens - Stripe owned payment method IDs in the form of (pm_123) or the network tokens in the doc you shared