Three-letter ISO currency code (lowercase). Currently, only "usd" is supported.

The Payment Token received from the Pro-Life Payments.js SDK.

For card payments only. Specifies when to capture funds from the customer’s account. automatic: Captures funds instantly upon payment authorization. manual: Places a hold on funds at authorization but captures them later.

A custom string you can attach to the object, useful for displaying information to users.

The email address where the payment receipt will be sent. If provided, a receipt will be sent to this email address regardless of other email settings.

By including this parameter, you're indicating your intention to use this PaymentRequest's payment method for future payments. When successful, providing this parameter will link the payment method to the PaymentRequest's Customer (if available). If no Customer was provided initially, the payment method can still be linked to a Customer after the transaction. Choose between: off_session: If the customer's presence in the checkout flow is uncertain. on_session: If you only plan to reuse the payment method when the customer is present during checkout.

The customer ID that the paymentToken or paymentMethod belongs to. If both the paymentToken and the setupFutureUsage fields are provided, the customer will be attached to the paymentMethod.

The ID of the payment method associated with the Customer used in this PaymentRequest.

Information to be shown in the cardholder’s bank statement. It will be concatenated with a short version of the merchant’s DBA Name.

Whether the transaction should be treated as a level 2 or level 3 transaction.

A unique identifier to ensure the same operation isn't processed multiple times, preventing duplicate transactions.

Specifies the account for which the Payment Request funds are intended. This is used for scenarios where one partner processes payments on behalf of another partner, such as in PayFac or related partner relationships.