#krishna-awate_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/1504741648406679563
📝 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.
- krishna-awate_api, 9 minutes ago, 9 messages
integrate custom checkout model not standard one.
Could you clarify what you mean by this? I shared some documentation previously—did that not address your requirements?
What do you mean by custom checkout? are you talking about creating your own form inputs to collect card details?
Right.
Collecting your Customer's card details and then sending raw card number via Stripe API is not allowed by default due to the PCI compliance. Your business is only allowed to send raw card details with following conditions::
- If you fully outsource this activity to a PCI DSS-compliant third party, please provide the name of that service provider.
- One of the following documents:
a) A current, complete PCI DSS Self-assessment Questionnaire (SAQ) D.
b) If you meet the qualifications of a Level 1 Merchant or Service Provider, a current PCI DSS Attestation of Compliance for Onsite Assessment.
c) If you fully outsource the handling of card data to a PCI DSS-compliant third-party service provider, only accept online or mail order/telephone order (MOTO) payments, and otherwise qualify, a Self-Assessment Questionnaire (SAQ) A. This document must list your entity's information and list the third-party service provider in Part 2f.
**If you're not in any of the conditions, you must use Stripe interfaces to collect card details. **
If you are, please refer to the guide here to request for the access: https://support.stripe.com/questions/enabling-access-to-raw-card-data-apis
Can I integrate API and check in test mode without providng PCI DSS-compliant
Unfortunately that is also not possible, this is stated in our docs here: https://support.stripe.com/questions/enabling-access-to-raw-card-data-apis