When a customer saves their payment method for automatic payment, a ZP Authorization record is created in NetSuite and connected to a ZP Customer Profile the next time the ‘Process Authorizations’ automation runs. Together these records represent the authorization to automatically pay future Invoices using the payment method saved by the customer.
Review Authorization records from Transactions > Zone Payments > Payment Authorization, or directly from the Payment Provider Activity and Customer record. This record shares high level details about the payment method saved with your payment provider.
Note: Payment methods are never stored directly in NetSuite.
Anytime a customer updates the payment method on file for automatic payments, the prior Authorization record is terminated and replaced with a new Authorization record.
Authorization Application
Authorizations have two application pathways. Saved payment methods can be applied broadly or to a group of Transactions (subscription, contract, Invoices created from the same Sales Order, etc.). If no Payment Group is present on the Transaction, the Authorization is designated to the Default Autopay Method. If a Transaction has a Payment Group ID, the Authorization will apply to the Payment Group.
- If Default Autopay Method is set on an Authorization record it will be used as the default payment method for automatic payments for the Customer Profile. There can only be one default for each Customer Profile. Using Default Autopay Method requires enabling the ZP Preference : “Autopay Using Customer Default”.
- A Payment Group is an ID used to identify a series of recurring payments. Generally, this would be equivalent to a subscription or contract. An Authorization record can be applied to specific Payment Groups to ensure that it will only be used to make automatic payments against records in the group. ZonePayments includes a Transaction field “ZP Payment Group ID” that can be used to identify the group an Invoice belongs to.
Authorization Records FAQ
Q: Why does my customer have multiple Authorizations and Customer Profiles on file?
A. If your company has multi-subsidiary customers, it’s possible that the customer has saved their payment method on file for multiple lines of businesses, which transact with different accounts in Stripe. When this occurs, the system automatically creates Customer Profiles to reference where each payment method is stored in Stripe. Additionally, anytime a saved payment is updated, the prior Authorization record is termed but remains accessible in the system.