RevenueCat / RevenueCat/react-native-purchases

Repeated POST API calls to https://m.stripe.com/6 - for fraud detection?

Open
#1,512 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
TypeScript
Stars
1.2k
Forks
117
Avg merge
14h 40m
Merged PRs (30d)
40

Description

Describe the bug
I am noticing unexpected and repeated network traffic to https://m.stripe.com/6 (POST API calls) in my React Native application after installing and configuring react-native-purchases for RevenueCat. These calls occur on every screen navigation or page visit. I am not using the Stripe SDK (@stripe/stripe-react-native) and have no other Stripe dependencies in my project. I am strictly using react-native-purchases and react-native-purchases-ui. The response that I get back from the POST API calls looks like this:

{
"muid": "23af3fc9-52c2-4216-8128-7f587f1554bcf6dc81",
"guid": "aa394064-aec0-405f-b710-7dc69589cb9618b820",
"sid": "d1f730b0-1a5f-48ec-a85f-8004cdd99d10c3ec8c"
}

  1. Environment
    1. Platform: Web
    2. SDK version: 9.6.9
    3. OS version: macOS Tahoe version 26.1
    4. Xcode/Android Studio version: Xcode Version 26.0.1 (17A400)
    5. React Native version: React Native: 0.81.5, Expo SDK: 54.0.21, React: 19.1.0
    6. SDK installation (CocoaPods + version or manual): manual
    7. How widespread is the issue. Percentage of devices affected. - I'm still in development, no devices yet.
  2. Debug logs that reproduce the issue - no debug logs.
  3. Steps to reproduce, with a description of expected vs. actual behavior - just use the latest react-native-purchases SDK.
  4. Other information (e.g. stacktraces, related issues, suggestions how to fix, links for us to have context, eg. stackoverflow, etc.)

Additional context
Is this expected behavior OR is there a way to disable advanced fraud detection in Stripe, if that is what this is.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the repeated POST requests using the reported React Native, Expo, and Purchases SDK versions, then inspect the network activity and SDK dependency behavior. Confirm whether the requests are expected, identify their source, and document whether a supported way to disable them exists.

Written by the indexing model from the issue text.

Assessment

Tech stack
react-native, typescript
Domain
mobile-dev, web-dev
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.