Knowledgebase

Payments and Commerce Frameworks Print

  • appletechnology, apple, billing, domainrenewal, restore, refund, guide, howto
  • 0

Taking money.

WHAT THE PLATFORM PAYMENT SYSTEM PROVIDES

Payment authorised on device, with card details never shared with you.

WHAT IT SUITS

Physical goods and services delivered outside the application.

WHAT IN-APPLICATION PURCHASING IS FOR

Digital goods and services consumed within the application.

WHAT THE RULES REQUIRE

Generally, digital goods must use the platform's purchasing, with a commission.

WHAT TO ESTABLISH BEFORE BUILDING

Which category your product falls into, and what the current rules permit.

WHY CURRENTLY

These rules change, and have been subject to regulatory intervention.

WHAT PURCHASE TYPES EXIST

Consumable, purchased repeatedly Non-consumable, purchased once Subscriptions, renewing

WHAT TO IMPLEMENT

Server-side verification of every transaction.

WHY

Client-side verification is trivially bypassed.

WHAT TO HANDLE

Purchases interrupted partway Restoring previous purchases Refunds and cancellations Subscription state changing outside the application

WHAT TO CONSIDER LOCALLY

Whether your users have payment methods the platform accepts.

WHAT TO NEVER DO

Direct users to external payment in ways the rules prohibit.


Was this answer helpful?
Back

Are you happy with your experience? Leave us a review on Trustpilot.


Trustpilot