Skip to content

Question about handling purchase #276

@kultie

Description

@kultie

Hi, I'm currently integrate qonversion into our apps and I dig through the documents but still got confuse how to handle purchase callback
I need guideline to handling consumable and non-consumable for handling purchase
These are what I understand from test environment:

  • Consumable if not link with any Entitlements won't appear in Purchase callback and rely if no error then purchase is sucesss
  • For deferred purchase consumable since the product is not link to any Entitlements the UpdatedEntitlementsReceived does not contain any information about the deferred product

So I have questions
1 .What should good practice to handle consumable?

  • Linking each Consumable with each Entitlements
  • Link multiple Consumable with 1 Consumable Entitlement.
  1. For 1 entitlement that link with multiple consumables how does I process to check for deferred purchase if I purchase those consumable products in 1 session and choose to simulate deferred purchase on android.

  2. What the difference between Entitlement that link with Consumable and Entitlement that link with Non-Consumable?

  3. How does Qonversion handle the status of Non-Consumable to prevent user purchase the Non-Consumable again or the app is responsible for check if use has Entitlement of Non-Consumable is activated?

  4. Every callback from Purchase, CheckEntitlements, HandleEntitlementsUpdated have dictionary of Active(?) entitlement or entitlement that qonversion have info?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions