#andrewl1030

1 messages · Page 1 of 1 (latest)

soft cosmosBOT
somber shoal
#

Test mode and live mode objects are different objects with different states, so I believe this is expected. Do you have request IDs for both the requests?

Here's how you can find a request ID: https://support.stripe.com/questions/finding-the-id-for-an-api-request

Finding the ID for an API Request : Stripe: Help & Support

Find help and support for Stripe. Our support center provides answers on all types of situations, including account information, charges and refunds, and subscriptions information. Get your questions answered and find international support for Stripe.

normal otter
#

Live mode request_id: req_dqf2qj9F3icCcD
Test mode request_id: req_MwGU6KaXF2MszU

#

I've checked that the business profile details exist in the connected account's settings under both live mode and test mode, so would expect the info to show up when using my test mode api key too

somber shoal
#

Can you set it on test mode and check if it shows up?

normal otter
somber shoal
#

Very odd... hmmm.... let me dig and circle back

normal otter
#

just to clarify, i am logged in to the connected account and viewing business profile data via https://dashboard.stripe.com/settings/public.

However, if i am logged into my primary account (which hosts my app) and viewing the connected account through the Connect tab, the Contact Information for the connected account is empty (so Doing business as is empty)

Stripe Login | Sign in to the Stripe Dashboard

Sign in to the Stripe Dashboard to manage business payments and operations in your account. Manage payments and refunds, respond to disputes and more.

somber shoal
#

Can you send a screenshot of the full browser for both the places you're looking? These might be entirely different fields

normal otter
somber shoal
#

I'm actually not sure how those 2 fields line up. What's the payload for the Account requests you made above? (apologies, we can't see GET request logs on our end)

normal otter
#

Im using the python stripe client and am only passing in the account_id that i am looking up

somber shoal
#

Right, but you mentioned above that the GET requests for test mode and live mode weren't lining up, so I wanted to see the payload from each to confirm

normal otter
#

the only differences between the requests are the API keys used

somber shoal
#

Right, but if the payload is different, then there has to be a reason, so I want to look at the actual payload to troubleshoot

normal otter
#

but the payloads arent different

#

oh are you referring to the payloads received, aka the response?

somber shoal
#

Yes

normal otter
#

Test mode payload:

{
  "capabilities": {
    "acss_debit_payments": "active",
    "affirm_payments": "active",
    "afterpay_clearpay_payments": "active",
    "bancontact_payments": "active",
    "card_payments": "active",
    "cartes_bancaires_payments": "pending",
    "eps_payments": "active",
    "giropay_payments": "active",
    "ideal_payments": "active",
    "link_payments": "active",
    "p24_payments": "active",
    "sepa_debit_payments": "active",
    "sofort_payments": "active",
    "transfers": "active",
    "us_bank_account_ach_payments": "active"
  },
  "charges_enabled": true,
  "country": "US",
  "default_currency": "usd",
  "details_submitted": true,
  "future_requirements": {
    "alternatives": [],
    "current_deadline": null,
    "currently_due": [],
    "disabled_reason": null,
    "errors": [],
    "eventually_due": [],
    "past_due": [],
    "pending_verification": []
  },
  "id": "acct_1MjoAIDJPUOxxsft",
  "object": "account",
  "payouts_enabled": true,
  "requirements": {
    "alternatives": [],
    "current_deadline": null,
    "currently_due": [],
    "disabled_reason": null,
    "errors": [],
    "eventually_due": [],
    "past_due": [],
    "pending_verification": []
  },
  "settings": {
    "bacs_debit_payments": {},
    "branding": {
      "icon": null,
      "logo": null,
      "primary_color": null,
      "secondary_color": null
    },
    "card_issuing": {
      "tos_acceptance": {
        "date": null,
        "ip": null
      }
    },
    "card_payments": {
      "statement_descriptor_prefix": "SOFTWARE",
      "statement_descriptor_prefix_kana": null,
      "statement_descriptor_prefix_kanji": null
    },
    "dashboard": {
      "display_name": "Mango Labs",
      "timezone": "America/New_York"
    },
    "payments": {
      "statement_descriptor": "MANGO LABS",
      "statement_descriptor_kana": null,
      "statement_descriptor_kanji": null
    },
    "sepa_debit_payments": {}
  },
  "type": "standard"
}
📎 message.txt
somber shoal
#

Okay, so to circle back and confirm my understanding. You want to know what the business_profile hash isn't showing up in test mode, yes?

normal otter
#

yes

somber shoal
#

Okay, going to test some stuff and get back to you

#

Hmmm, I'm able to get the business_profile when I retrieve in test mode. Let me check one other thing

soft cosmosBOT
somber shoal
#

Yeah, I'm not sure why it's not showing up in test mode. That's really odd. Let me get someone else to weigh in and then we can go from there

#

okay, so this looks like intended behavior

#

It looks like we redact that information if it exists in live mode. The problem I had when reproducing on my end is that my Account didn't have any live mode data, so that's why I got business_profile, but you didn't. Here's a list of things we redact from test mode requests (if they exist in live mode)

Specifically:

Account
business_profile
company
email
external_accounts
metadata
tos_acceptance
controller

Person (used for accounts with individual / sole_prop business types)
address
dob
email
first_name
id_number_provided
last_name
metadata
relationship
requirements
ssn_last_4_provided
verification

normal otter
#

Ok, thanks for figuring that out