-
Notifications
You must be signed in to change notification settings - Fork 1k
AuthorizeNet Plugin
AuthorizeNet connects AVideo payment/subscription flows to an Authorize.Net merchant account. Payment configuration is high risk: test in sandbox and confirm the current provider requirements before accepting real money.
- Obtain an Authorize.Net merchant account and current API credentials from its official dashboard.
- Back up AVideo and enable the payment/wallet/subscription plugins required by your intended flow.
- Enable
AuthorizeNetand start withsandboxenabled. - Enter
apiLoginId,transactionKeyandsignatureKey; customize button labels if desired. - Complete successful, declined, cancelled, recurring and refund/cancellation tests.
- Confirm AVideo grants access only after a verified provider response.
- Move to production credentials only after reconciliation and webhook/signature tests pass.
Never place merchant credentials in browser code, screenshots or public logs. Restrict access to the plugin configuration and rotate exposed keys.
A card was charged but access is missing: do not charge again. Match the provider transaction ID to AVideo/payment logs and reconcile deliberately.
Sandbox works but production fails: sandbox and production have different credentials/endpoints and merchant settings.
Can AVideo store card numbers? Do not design a flow that sends/stores raw card data in AVideo unless the provider's supported hosted/tokenized flow and your compliance obligations explicitly allow it.
| Plugin | Added value |
|---|---|
| YPTWallet | Gives paid features and users a shared wallet balance. |
| Subscription | Sells recurring access to premium content. |
| PayPerView | Sells one video or event at a time. |