In-store and online
Authentication
Errors
Stronghold.Pay.JS
Postman Collection
Charge Authorization
PaymentSources
BalanceTransfers
Context
Customers
PayLinks
Charges
Reports
Sandbox
Settlements
Tips
Utility
Models
Countries
Currencies

Charge Authorization

Proper authorization must be obtained from the customer to comply with the appropriate regulations.

Authorization should be obtained during checkout, and before the charge is authorized on the API; created an authorized charge indicates that the customer has given authorization.

Card Authorization Requirements

Ecommerce

Terms & Conditions for card payment must be linked to from the payment page. Please contact your account representative for information on whether your ecommerce setup sufficiently covers card authorization requirements.

In Store

Please contact your account representative for information on how authorization works with your integration.

ACH Authorization Requirements

Payments made via ACH (i.e. the payment source type is bank) require the user to be presented with certain information in order to comply with the appropriate NACHA regulations.

Ecommerce

The simplest form authorization can take is adding some language near the checkout/pay button on the order. Suggested language:

By clicking the button above, you authorize {MerchantName} to electonically debit your {paymentSource.Label} for ${charge.amount}.

{MerchantName} should either be the ‘display name’ associated with the merchant (business name/DBA) or the name of the licensed entity. Preferrably, the name the users identifies the merchant as.

The resulting message would read, for example:

By clicking the button above, you authorize BestMerchant to electonically debit your BankFI, NA. checking ending in 1234 for $105.35.

If you wish to use custom language or authorization methods, please contact Stronghold.

In Store

Please contact your account representative for information on how authorization works with your integration.