PayNowPro

Customers

Learn about Customer objects in PayNowPro, how to link them to your users with associatedId, and manage payment history and subscriptions.

The Customer object is the logical representation of your end-users within the PayNowPro ecosystem. By creating Customer objects, you can store reusable payment information, track payment history, and manage subscriptions for individuals. Each Customer object in PayNowPro should map directly to a user record in your own system's database.

Creating a Customer is a required first step before you can use the modern Subscriptions API.

The Associated ID

When creating a Customer, you must provide an associatedId. This ID is a unique identifier from your own system —for example, the primary key or UUID of the user from your application's database.

This allows you to easily link and verify the PayNowPro Customer object with your internal user records. When you need to fetch or update customer data, you can use this associatedId to ensure you're retrieving information for the correct user.

Key Distinction: associatedId vs. customerId

It is crucial to understand the difference between these two identifiers:

  • associatedId: An identifier provided by you. It is the unique ID for a user as they exist in your application.
  • customerId: An identifier generated by PayNowPro. It is the unique ID for the object once it has been created in our system. You will receive this ID in the API response after creating a customer.

Why Use Customer Objects?

Effectively using Customer objects is foundational to leveraging the full power of PayNowPro:

  • Subscription Management: Customer objects are required to attach recurring subscription plans to your users.
  • Payment History: You can easily view all historical transactions for a specific user in one place.

Next Steps

Now that you understand how to represent your users, learn how to attach recurring plans to them.

On this page