Payment Intents

A Payment Intent is an object that represents your intention to collect a payment from a customer. Think of it as a detailed instruction manual for a single transaction; it tracks the entire lifecycle of a payment, from its creation to its completion.

Creating a Payment Intent is the first step in any payment process. You must create one before you can collect funds. This object contains crucial information that guides PayNowPro on how to handle the transaction, including (but not limited to):

• The amount to be collected and the currency.
• The customer's name.
• The reason for the purchase.
• Whether the payment is a one-time charge or part of a recurring subscription.

The Payment Lifecycle

Once a Payment Intent is created, it initiates a secure, three-step process designed to make payment collection simple and safe.

1. Create the Intent on Your Server You begin by making an API call from your server to PayNowPro, providing all the necessary details for the transaction (amount, customer info, etc.). PayNowPro will respond with a unique intentId.

2. Redirect the Customer to PayNowPro Using the intentId from the previous step, you redirect your customer to a secure payment page hosted by PayNowPro. This means you don't have to handle or store sensitive credit card details directly, greatly simplifying your PCI compliance.

3. Process Payment & Return to Your Site On the PayNowPro page, the customer enters their credit card and billing information to complete the payment. After the transaction is successfully processed, we will redirect the customer back to the redirectUrl you specified when creating the intent. This is typically a success or order confirmation page on your website.

---

A Note on Your Tenant Alias

When you sign up for a PayNowPro account, you are assigned a unique identifier called a Tenant Alias. This alias represents your business or application within our system.

It is essential to include your Tenant Alias whenever you interact with the PayNowPro API. It tells us which merchant account is making the request, ensuring your data and transactions are securely routed and managed. You must provide it when creating Payment Intents and in all other API calls.