# Online payments

> Choose between Checkout, the Charge API, and mobile SDKs to accept payments online.

Every online payment follows the same lifecycle: your server initializes it, the customer completes it, and your server verifies it before you deliver value. See [Payment flow](/payments/concepts/payment-flow) for each stage.

New to Paystack? Start with [Build your first checkout](/payments/online/quickstart).

There are three main ways to integrate online payments:

## Checkout

Paystack hosts the payment page and channel selection. Choose it for broad payment method coverage with the least implementation effort.

- [Checkout overview](/payments/online/checkout)

## Charge API

You build the payment UI and respond to each prompt Paystack returns. Choose it when your product owns the payment experience.

- [Charge API overview](/payments/online/charge-api)
- [Charge cards](/payments/online/charge-api/cards)

## Mobile SDKs

Mobile SDKs fit native apps where you still want a Paystack-managed payment surface. Your server initializes the transaction, your app receives an `access_code`, and the SDK completes the payment in a native flow.

- [Android](/developer-tools/mobile-sdks/android)
- [iOS](/developer-tools/mobile-sdks/ios)
- [Flutter](/developer-tools/mobile-sdks/flutter)

As a rule of thumb: choose Checkout for speed, Charge API for control, and mobile SDKs for native app experiences. After that, add channel-specific capabilities such as [recurring charges](/payments/recurring/charge-authorization), [bulk charges](/payments/recurring/bulk-charge), [Apple Pay](/payments/channels/apple-pay), [partial debits](/payments/recurring/charge-authorization/partial-debits), or custom [metadata](/payments/online/metadata) when your business model requires them.
