Viva.com Payments for Blesta is delivered as two cooperating extensions. Understanding the split
explains where every credential, setting, and log entry lives.

The gateway — viva_wallet_gateway

A thin nonmerchant gateway. On the invoice payment page it renders a single redirect button —
Pay with Viva.com when the client already has a saved token, or Pay & save with Viva.com
otherwise. It holds no credentials and makes no API calls. Its callback URL also answers
Viva's webhooks and URL-verification handshake.

The manager plugin — viva_wallet_manager

The engine. It stores the encrypted Viva credentials, runs the hosted Smart Checkout, keeps the
per-client recurring token, receives verified webhooks, and runs its own daily cron to charge
saved tokens on renewal (plus refunds, voids and captures).

Why two parts

Blesta forces a trade-off: a nonmerchant gateway gives the full hosted-redirect checkout but has
no hook Blesta can call unattended, so it can't auto-renew. A merchant gateway can auto-charge a
stored token but captures the card through an inline widget, not a redirect. Pairing a redirect
gateway with a companion manager plugin gives both: hosted checkout and true automatic
renewals.