Purchasely
4.4
4.4
  • Welcome page
  • General
    • Presentation
    • Release notes
  • Quick start
    • Console Configuration
    • SDK Implementation
    • Testing
    • Sample
  • Basic configuration
    • Console Configuration
      • Creating a new application
      • Creating your Products
        • App Store
        • Play Store
        • Huawei App Gallery
        • Amazon App Store
        • Products & Plans
      • Design your Paywalls
      • Design your Paywalls-Latest
        • Carousel
        • Carousel Flow
        • Features List
        • Features List & Plan Picker with 2 & 3 columns
        • Feature list overlay
        • Plan picker horizontal
        • Plan picker with 2 and 3 Column
    • SDK installation
      • iOS SDK
      • Android SDK
      • React Native SDK
      • Cordova SDK
      • Flutter SDK
      • Unity SDK
    • SDK configurations
      • Paywall observer mode
      • Full mode
      • StoreKit 2
      • Appendices
        • Start the SDK
        • Set User Id
        • Notify when the app is ready
        • Present paywalls
        • Unlock content / service
        • Close SDK (Android only)
    • Stripe
    • Purchasely with RevenueCat
  • S2S notifications
    • Server-to-server notifications ?
    • Apple App Store
    • Google Play Store
    • Huawei App Gallery
  • Analytics
    • Dashboards
      • Introduction
      • Live
      • Subscriptions
      • Cohorts
      • Trials
      • Events
    • Events
      • Webhook events
        • Subscription events
        • Subscription events attributes
      • SDK events
        • UI events
        • UI attributes
  • Integrations
    • Webhook
      • Receiving and understanding messages
      • Managing entitlements
      • Detailed sequence diagrams
    • Airship
    • Amplitude
    • AppsFlyer
    • Adjust
    • Piano analytics(ex AT Internet)
    • Batch
    • Branch
    • Braze
    • Clevertap
    • Customer.io
    • Firebase
    • Iterable
    • Mixpanel
    • MoEngage
    • OneSignal
    • Segment
    • Brevo(ex Sendinblue)
  • Advanced Features
    • Asynchronous paywalls
    • NEW: Promotional offers
    • Anonymous user
    • Associating content
    • Audiences
    • Customising UI
      • Errors & alerts
      • Controllers (iOS) / Fragments (Android)
    • Deeplinks automations
    • Disable placements
    • Displaying users subscriptions
    • Localization
    • Lottie animations
    • Non-subscription products
    • Paywall action interceptor
    • Promoting your products
      • Self-promotion
      • Promoting In-App Purchases
    • Purchase manually
    • Subscription status
    • Use your own paywall
  • Others
    • Frequently Asked Questions
    • Migration guides
      • Migrate to Purchasely
      • Webhook
        • Migrate to Webhook v3.0
      • SDK
        • Migrate to SDK v3.0
          • v2.2.0
          • v2.1.3
        • Migrate to SDK v3.1
        • Migrate to SDK v3.2
        • Migrate to SDK v4.0.0
  • TESTING
    • Testing Cycle Durations
Powered by GitBook

© Purchasely 2020-2023

On this page
  • What are server-to-server notifications ?
  • What's the challenge in implementing them ?
  • How does it work with Purchasely ?
  • How do I activate server-to-server notifications using Purchasely ?

Was this helpful?

Edit on GitHub
  1. S2S notifications

Server-to-server notifications ?

PreviousPurchasely with RevenueCatNextApple App Store

Last updated 1 year ago

Was this helpful?

Server-to-server notifications are available on each Applications Store, to get real-time notifications of purchases, renewing…

What are server-to-server notifications ?

They consist in messages, sent by the Applications Stores, every time an event occurs on a subscription. For instance, a message is sent when a subscription :

  • is purchased

  • is renewed

  • is cancelled (auto-renewing cancelled by user for the following billing period)

  • is refund

  • gets expired

  • encounters a billing issue

  • …

The server-to-server notifications are not mandatory for making subscriptions work, but they are very valuable in the sense that they bring a real-time and comprehensive vision for the app editor.

What's the challenge in implementing them ?

The difficult part in integrating server-to-server notifications is the following :

  1. it is quite (in fact very !) complex. There are lots of different messages, edge cases that need to be implemented

  2. it has a totally different behaviour between the App Store and the Play Store, which brings even more complexity

When developing their IAP solution in-house, most app makers do not implement these server-to-server notifications, which prevent them from :

  • Having a real time vision of their subscribers base

  • Leverage on this to mitigate churn and optimise revenues

  • Avoid user fraud consisting in getting a yearly subscription and getting refund quickly for it

How does it work with Purchasely ?

Purchasely Cloud Platform works as a middleware between the Mobile Applications Stores and your own platform :

  • It is connected to the stores and is the recipient of the S2S notifications

  • It translates these store specific notifications into a common simple language

  • It forwards every notification received directly on the Webhook to your own backend

The benefits for you is that, instead of having several notifications systems to implement, you can focus on one single and simpler interface. More over, as more stores are integrated into Purchasely product, there notifications are translated into the same common language, which means that you have nothing to do on your side !

How do I activate server-to-server notifications using Purchasely ?

In order to activate server-to-server on Purchasely, you need to connect each of your stores to the Purchasely Cloud Platform.

Here are the guides to connect each store :

Apple App Store
Google Play Store
Huawei App Gallery