#satyashetty
1 messages · Page 1 of 1 (latest)
Hello! We'll be with you shortly. 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.
- satyashetty, 1 hour ago, 6 messages
- satyashetty, 4 hours ago, 18 messages
- satyashetty, 5 hours ago, 5 messages
- satyashetty, 3 days ago, 21 messages
You're not sending the expand parameter. It's unchecked in Postman
ok
You need to check the box on the far left of the row to actual enable the parameter
"error": {
"message": "Invalid array",
"param": "expand",
"request_log_url": "https://dashboard.stripe.com/test/logs/req_CXzRo0JugWQxwT?t=1708421033",
"type": "invalid_request_error"
}
}
Sign in to the Stripe Dashboard to manage business payments and operations in your account. Manage payments and refunds, respond to disputes and more.
i get this when i check the box
Looks like Postman is applying some formatting to the string: https://dashboard.stripe.com/test/logs/req_CXzRo0JugWQxwT
Sign in to the Stripe Dashboard to manage business payments and operations in your account. Manage payments and refunds, respond to disputes and more.
Ok, you're sending them as query parameters. You need to send it in the body
ok
The Stripe API is organized around REST. Our API has predictable resource-oriented URLs, accepts form-encoded request bodies, returns JSON-encoded responses, and uses standard HTTP response codes, authentication, and verbs.
https://docs.stripe.com/api#:~:text=The Stripe API is organized around REST. Our API has predictable resource-oriented URLs%2C accepts form-encoded request bodies%2C returns JSON-encoded responses%2C and uses standard HTTP response codes%2C authentication%2C and verbs.
Complete reference documentation for the Stripe API. Includes code snippets and examples for our Python, Java, PHP, Node.js, Go, Ruby, and .NET libraries.
let me try form encoded and check
this is a GET request do i still use a form encoded data?
You've checked the wrong box: x-www-form-urlencoded
Your payload is still wrong. It expects an array, which in form-urlencoded payloads looks like:
expand[0]: payment_intent
I just told you
it works now thanks, so if payment fails for some reason for ex: 3ds Secure auth failure then requires_action will be populated in this section?
Yes, payment_intent[status] will be requires_action