Solved

`POST /v1/receipts` failing with Server-Side observer mode

  • 3 May 2023
  • 2 replies
  • 151 views
D
Badge +3

Hi there!

Can you please clarify the case of using RC with the Server-Side observer mode?

Prerequisites:

  • Apple App Store Server Notification is configured
  • Google Real-Time Developer Notifications is configured
  • Webhooks are configured

The happy-path looks like:

  • Our app (Android/iOS) completes a purchase for a new user and gets the fetch token/receipt
  • Our app sends all needed data (app_user_id, fetch_token, price/currency, product_id) to our backend
  • Our backend invokes POST /v1/receipts
  • Our webhook receives the initial_purchase event

What will happen if our backend doesn't invoke POST /v1/receipts due to a network error or internal error:

  • Will the initial_purchase event be raised anyway for that new user?
  • Will any future events be automatically detected for that user?
  • Should we guarantee to invoke POST /v1/receipts to ensure correct behavior?

 

icon

Best answer by Michael Fogel 5 May 2023, 19:14

View original

2 replies

Michael Fogel
Rank
Userlevel 4
Badge +6

Hey There! 

 

You should guarantee to invoke the receipts endpoint. If you dont have this endpoint hit for that user, that subscription will most likely not be tracked as this endpoint handles recording a purchase for a user from iOS, Android, or Stripe and will also create that user if they don't already exist in RevenueCat.

 

If you do use this endpoint, that user will be trackable in the dashboard and the purchases will be tracked consistently.  

L
Badge

Hello Michael, i would love to get some more informations about this. We have the same setup as dmitry.

For Stripe the /v1/receipts process is documentated here: https://www.revenuecat.com/docs/getting-started/stripe#5-send-stripe-tokens-to-revenuecat

For Apple and Android it looks unnecessary to call this endpoint (/v1/receipts) - there is no info in the docs about this?. Does purchases_flutter handle this for me? 

Please clarify, thanks!

 

Reply


Terms & ConditionsCookie settings