Skip to content

Step 4. Verify receipts

Verify the validity of the receipt received after the payment is completed and whether it has been forged or tampered with. This blocks fraudulent purchase attempts through hacking or payment manipulation and ensures the reliability of payment data. Deliver products to users only after verification passes.

Receipt verification flow

The app server requests receipt verification by calling the receipt verification API of the Hive Axyl Server API. The app client sends the values required for verification to the app server, and the app server receives the verification result directly without going through the app client.

  1. The app client sends the receipt and purchase information received from the store to the app server.
  2. The app server requests receipt verification from the Hive Axyl server with the Hive Axyl Server API.
  3. The Hive Axyl server rechecks the receipt with Google Play and returns the verification result to the app server.
  4. The app server checks the verification result and returns the values required for step 5 to the app client.

Depending on the product type, receipt verification is divided into consumable product receipt verification and subscription product receipt verification. For consumable products, a receipt is issued for each purchase, and for subscription products, a receipt that represents the subscription status is issued.

Implementation order

Follow the steps below to verify Google receipts.

  1. Prepare receipt information
    • Collect the receipt verification request values in the app client and send them to the app server
  2. Verify receipts with the Hive Axyl Server API

When receipt verification is complete, proceed to Step 5. Deliver products and finish transactions.