[PAID] Google Play Billing - In App Purchases [Version 5] 🔥

Google Play’s billing system with SDK Version 5 :partying_face:
Extension that enables you to use Billing system that enables you to sell Digital products in your app.

Note: Starting on August 2, 2022, all new apps must use Billing Library version 4 or newer. By November 1, 2022, all updates to existing apps must use Billing Library version 4 or newer. Source → Pura Vida Apps


Functions


component_method

  • Establishes the connection to the Google Play Billing Client.

Block

  • This block uses the Google Billing API to alert users if a transaction is failed, and tells them to update the Payment methods.

  • It can be called when the Screen Initializes or when any purchase is successful and after acknowledgement.

component_method(1)

  • Is Purchased block to check if the user is subscribed or purchased a product.
    • product: product id, e.g. android.test.purchased
    • type: type of the product, 1 = inapp, 2 = subsiption

Warning: The block is implemented in such a way that, an asynchronous operation is fired (according to the billing v5) then the app shall wait for the operation to complete.

component_method(2)

  • Queries the information about the given product.
    • product: product id, e.g. android.test.purchased
    • type: type of the product, 1 = inapp, 2 = subsiption

component_method(3)

  • Purchase block, that enables the user to purchase or do a subscription to a product.
    • product: product id, e.g. android.test.purchased
    • tokenOffer: token offer required for the purchase, can be empty.
    • type: type of the product, 1 = inapp, 2 = subsiption

component_method(4)

  • Block to get a property from the product (e.g. formatted_price…)
    • product: the product object to retrive the property from.
    • name: the name of the property

component_method(5)

component_method(6)

  • Blocks to acknowledge a non-consumable (purchases that can be only done once) purchase or a consumable (purchase that can be made again) purchase.
    • purchase: the purchase product to acknwoledge
    • ackId: Or the acknowledged Id, will be returned by the event to distinguish multiple requests.

Event block fired when the Purchase is completed by the user after calling the @Purchase block.

component_event(1)

Fired when the user cancels the purchase in middle of the translation. Such as dismissing the Dialog.

component_event(2)

Block that returns the info of the product, (from @Query block).

component_event(3)

Block to report the failure of the attempt to retrieve the product info.

component_event(4)

Block to report the launch of the Flow…(When the billing dialog is launched successfully, this block is fired.)

component_event(5)

Fired after the product acknowledge result is returned.
response Code = 0, states that it was successfully acknowledged.

component_event(6)

After the Google Play Billing client is ready/error-ed, this block is fired.
isOkay = everything went right.

component_event(7)

Event fired after the Billing Service to the client got disconnected.


component_event(8)

  • This block is called when no action is needed and everything seems fine when we call the InAppMessages block.

SubscriptionUpdated

  • Called after InAppMessages detects a update of the subscription. A new purchase token is returned.

Screenshots


Blocks

Next

That’s it! The next roadmap; To implement the Google Play Rest API that allows to verify purchases more securely with the servers instead of relying on the Google Play data.

Purchase

If you are interested in the extension, you can write a message to me in the PM or reply in the topic, I’ll message you back.

Price: 1170 INR | 15 USD
Two of them: Billing Extension + Crash Reporter: 1500 INR | 18$

PayPal | PayTm (Message me) | Stripe


Thanks for @Baxolino for sponsoring the extension!
With @UnknownBeast and @Pradevel for testing :partying_face:

10 Likes

great extension. I love it . it’s easy to use​:relaxed::pray::fire::heart_eyes:

2 Likes

Nice extension boi :slight_smile:

2 Likes

If possible could you post a demo video…
A friend of mine is interested…

2 Likes


this is a trial purchase with the extension. I bought a subscription. :heart_eyes:

2 Likes

Version 1.1

  • Added In App Messages block

    Block

    • This block uses the Google Billing API to alert users if a transaction is failed, and tells them to update the Payment methods.

    • It can be called when the Screen Initializes or when any purchase is successful and after acknowledgement.

  • In App Messages result

    component_event(8)

    • This block is called when no action is needed and everything seems fine when we call the InAppMessages block.
  • Subscription Updated

    SubscriptionUpdated

    • Called after InAppMessages detects a update of the subscription. A new purchase token is returned.

Payment Methods

We accept PayPal, PayTm and Stripe.

2 Likes

Hi,
Im interested in puschasing the extension but has anyone actually managed to use the extension to implement a monthly subscription on an app in the play store?

Cheers
Steve

Yes, thats right, we have checked almost everything.
You can try out the extension before you buy it.

1 Like

the extension is used in a large app. the app has 270,000 downloads. purchases and subscriptions are successfully completed in the app every day

this is the app, you can test it and convince yourself of the extension