#colton_dashboard-manualpayments
keen tendonBOT
👋 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/1305566530561507430
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
fickle currentBOT
carmine yoke
Hi 👋 Customer Sessions are meant to be used by the end-customer, they are not meant to be used by merchants.
If they trigger 3DS challenges, you won't be able to complete those as those are supposed be completed by the customer.
Are you processing MOTO transactions (mail order/telephone order)? Is that why you need to be able to enter your customers card details for them?
spare bay
We're not processing MOTO transactions directly, but we want our Connect customers to have the option to manually input customer credit card information when needed. Most of our Connect customers are businesses working with vendors, and often these vendors provide their card information over the phone. This would allow our Connect customers to securely charge their vendors for current and future orders
carmine yoke
Gotcha, so sounds like you're trying to enable your Connected Accounts to process MOTO payments if they're accepting card details over the phone.
I think the best way to provide those currently is via the Stripe dashboard.
If you want to provide those details via an API-based integration, then I recommend reviewing how that will impact your PCI compliance burden and reach out to our Support team to request access to process raw PANs.
https://support.stripe.com/?contact=true
keen tendonBOT
daring badge
colton_dashboard-manualpayments
spare bay
Ok so this applies even if we just save the credit card as the default payment method?
daring badge
@spare bay not entirely sure what you mean unfortunately
spare bay
After reviewing the documentation at https://docs.stripe.com/security/guide#validating-pci-compliance on PCI compliance, I noticed recommendations to use Checkout, Elements, or client-side tokenization to reduce the compliance burden. Are there any specific Elements that could be used as an alternative to needing access to process raw PANs?
daring badge
@spare bay that's exactly what the doc covers, by mentioning Checkout or Elements as solutions for example.
I'm sorry you seem a bit lost about how to use Stripe and I'm not sure I understand your question
spare bay
I am using the Payment Element right now but the Payment element appears to only be used the for the end-customer to provide the credit card number. I am trying to figure out how i can use the Payment element or something similar that allows my connect customer to manually input the credit card for their customer. from what i understand the Payment element is meant for you to redirect the end-customer to the Payment element for them to enter their own credit card.
daring badge
Gotcha, so you do want to accept MOTO payments which is exactly what my colleague explained earlier. We have a feature for this and require access/approval for it. Please reach out to our support team as recommended earlier: https://support.stripe.com/contact and they can help you get access to this feature and build it for your merchants
spare bay
ok understood. Thank you for the help.