Skip to main content
A connected account’s customers belong to that account. Your platform creates and manages them with the platform secret key and the merchant’s ID, then uses the same merchant when it saves a card or takes a payment for that customer. Store the merchant ID next to each customer’s Ionic ID in your own records. Customer fields and operations are the same as in Manage customers.

Before you begin

  • A platform secret key from Connect → API keys, kept on your server.
  • An active connection in the same mode. The platform key and the merchant’s connection both grant each permission an operation needs:

Create the merchant’s customer

The customer belongs to that merchant and mode. Select the same merchant on every later request for this customer.

Save a card for the customer

Save a card with the customer’s consent using a SetupIntent and a Payment Block on your page. See Save cards for connected accounts. To offer saving during a payment instead, see Accept payments for connected accounts.

List the customer’s saved cards

Your application builds any saved-card selection on top of this list.

Choose the default card

An invoice that collects automatically charges the customer’s default payment method when the invoice names none. A subscription that collects automatically sets its own default_payment_method.
To stop a saved card from being used for new charges, revoke it with Revoke a payment method. A revocation requires a reason.

Customer events

A platform webhook endpoint receives a merchant’s customer.created, customer.updated, customer.deleted, and customer.restored events when that merchant’s connection grants customers:read. The event’s account field names the merchant. See Webhooks for platforms.

Keep customer data with the correct merchant

What’s next

Save cards

Save a card to a connected account’s customer with consent.

Read subscriptions and invoices

Read a connected account’s billing and gate access with entitlement.