The Payment API lets services charge users. For all users, credit card and in-app purchase are supported; Turkcell users can additionally be charged to invoice.
Choose the correct payment method for the product type: physical (credit card), digital (in-app purchase), data (invoice). Physical products cannot be sold with in-app purchase—must be digital.
If the service charges via credit card, it collects the products through messaging and calls Payment API with order details. Payment API shows the order, asks payment method and address, and completes with 3D secure card verification. The service is notified asynchronously after payment completes.
If the service uses in-app purchase, it collects the items via messaging. After user approval, Payment API redirects to the stores (App Store / Google Play). When purchase succeeds, the service is notified asynchronously.
Define company info for the seller, then product definitions. For credit card, multiple products per service are allowed. For in-app purchase, only one product per service (for now).
Name, address, and contact info of the seller.
When calling “Payment Service,” send the appropriate channel info:
Price, currency, logo URL, and product type (digital or physical).
Payment Service responses are sent asynchronously to the service callback URL.
Web service requests are JSON over HTTPS with HTTP Basic Authentication. Use the TES-provided username/password.
| Server | Environment | URL |
|---|---|---|
| PAYMENT | Production | https://apigw.tvoip.turkcell.com.tr/pgw |
| PAYMENT | Test | https://prpapigw.tvoip.turkcell.com.tr/ppgw |