In-App Purchase is one of Samsung services which can enable you to sell various items from inside your applications. In-App Purchase is only available for Android-based applications for Samsung Apps. Currently, it supports more than 60 countries with Credit card, P-SMS, and several local payment methods. To help you integrate In-App Purchase into your application, we provide guiding documents. Please read it thoroughly before you use In-App Purchase.

Release note

FAQ

• Show
  • What types of payment methods are supported by the Samsung In-App Purchase (IAP) library?

    Samsung IAP supports credit-card and phone-bill payment in countries where paid services are available.However, only small paymentsare allowed via mobile transaction, and you can only use prepaid cards in China.

  • What kinds of items are supported by Samsung IAP?

    Samsung IAP currently supports consumable items.Samsung plans to support non-consumable items and subscription items in the near future.v1.95.0 and previous versions support non-consumable items based on IMEI.Becauserestoration for those itemsis device-based, they are categorized between competitors' consumable items and non-consumable ones.From IAP v2.0, Samsung plans to support consumable items, non-consumable items (based on accounts), and subscription items.

    1. Consumable items:Disposable items for one-time use.They cannot be restored.
    2. Non-consumable items:Restorable items that are account-based.
  • Can I use Samsung IAP on non-Samsung devices?

    Currentlyyou cannot use Samsung IAP in non-Samsung devices.

  • Is it possible to encrypt transactions for item purchases?

    Encryption is not currently supported. Instead, encrypted server-to-server verification is supported for payment verification.

  • What kind of process is there to communicate with the server for item purchase transactions?

    As answered in Q4, server-to-server verification is supported.The verification process is explained in the In-App Purchase developer guide. It can be summarized as follows:

    1. Upon purchase, an encrypted token for the transaction is issued to the 3rd party app.
    2. As soon as the purchase is completed without any issues, the token is sent to the developer’s server.
    3. The token is sent from the developer’s server to the Samsung Apps verification server to verify the transaction.

    If the developer’s server flags the transaction as a normal purchase performed in the Samsung Apps server, the user can download the purchased item.

  • What is the “transactionId”parameter used for in an IAP request?

    The “transactionId” value distinguishes requests and responses for an IAP transaction.As a unique value set for each API call during the life cycle of an application, it ensures the stability ofthe application by guaranteeing one response perIAP request.

  • Are monthly payments supported by IAP?

    Periodicpayments,such as for subscriptions, are not supported in the current version.Samsung plans to support this in later version.

  • Which time zone determines the purchase date (getPurchaseDate)?

    The date is GMT-based; that is, GMT+0.More accurate dates are provided in the latest version(v.1.95.0).

  • How can I test an IAP during app development?

    You can test the payment process by setting developerFlagto 1 (success) or -1 (fail).Please note that you must set developerFlagto 0 (real payment) or delete itwhen you actually sell in your apps.

  • Is it possible to self-test an app under development in real mode, without submitting it to the seller's site?

    Real mode test is only available after the app is verified and distributed for public use.Before its distribution, you can call plasma.setDeveloperFlag(1) for payment testing in developer mode.If you test an undistributed app in real mode by setting developerFlagto 0, aSTATUS_CODE_ITEMGROUPIDNOTFOUND(9201) error occurs because there is no item distributed for public use.

  • Is it possible to prevent a purchased item from being purchased again?

    Whenever you start an app, make sure to check the ID of purchased items (requestPurchasedItemInformationList) to prevent duplicate payments.

    Please note that requestPurchasedItemInformationListkeeps a purchase list based on IMEI (International Mobile Equipment Identity), which makes it impossible to see the items purchased from non-Samsung devices and prevent duplicate payment.From the next version, Samsung plans to support payment types that are based on accounts in order to prevent duplicate payments.

  • Why does the 9218 error (failed purchase) occur when payment is made during the review of an app with the IAP library?

    The 9218 error is "unexpected access to QA with test mode" and occurs during the verification/authorization of an app. It happens when you upload the app to a seller’s site without deleting setDeveloperFlag(1) from the source code.

  • Can I get a refund for the payment made for testing?

    You can get a refund if you test the app in developer mode. However, you cannot get a refund for a real item you purchase in non-developer mode.For information about how to test in developer mode, please refer to Q9.