#Juili-payments
orchid crest
Hello! I'm not familiar with Boomi, but can you give me some details on what differences you're seeing?
strong cypress
When I look at both payment_intent response profiles (Prod and Test) I see a number of differences.
Eg: Balance_transaction
(In test mode I see that the Balance transaction is of the type Object but in Prod it just simple text)
TEST:
"balance_transaction": {
"id": "txn_3L19MZE0mU5Q7cyi0zJruYT6",
"object": "balance_transaction",
"amount": 300000,
"available_on": 1653264000,
"created": 1652966759,
"currency": "usd",.........
PROD:
"balance_transaction": "txn_3L0A0OG0mU9Q7cyi1u009fhR",
"billing_details": {
"address": {
"city": null,
"country": null,
"line1": null,
"line2": null,
In Boomi, I am using the response profile from Stripe to configure the Integration. As its being developed using test environment, there is a profile mismatch when I start pulling records from Production
orchid crest
Are you doing anything different about the two requests? Do you have the requests IDs for each of these requests? From a quick glance it looks like one request is expanding the Balance Transaction object, while the other is not, but being able to see the exact requests you're making would help me confirm
strong cypress
These logs are directly from the Stripe UI, one is for a Payment_intent I created in Test Environment and the Prod logs are from my client's environment.
orchid crest
Where in the Stripe UI are you seeing this? If these are requests you should be able to see a reqeust ID (of the form req_xxx)
orchid crest
and where are you getting the livemode one from?
orchid crest
Can you just share a more limited screenshot, that just shows which request/event you've selected (under the "All activity" section) - I don't need to see the response body? I specifically want to know if you're looking at a request or an event
strong cypress
Does this help?
I think I found the issue, let me update the response profile in Boomi and try again. Will reach out here if I am still unable to match the profiles
orchid crest
👍 Let me know if you find the issue - i'll take a quick look as well
orchid crest
@strong cypress just checking in - i also took a look and I think the issue is the requests your looking at were both creating through the dashboard, and depending on which specific flow you go through the dashboard sometimes chooses to expand certain attributes (which would make the response look different). If you were to make the responses through the API you wouldn't run into this issue unless you made the requests differently in live and test mode
To be specific, your test mode dashboard requests expands a lot of attributes (see expand in the request at https://dashboard.stripe.com/test/logs/req_TA6mrjgMTyvGrM) while your live mode request doesn't expand anything at all, so it's expected that those responses would look different