# `MishkaPay.Application`
[🔗](https://github.com/mishka-group/mishka_pay/blob/v0.0.1/lib/mishka_pay/application.ex#L5)

Mishka Pay's own processes: the task supervisor `MishkaPay.Credentials.fetch/3` runs a host's
keys plugins under, so a plugin that exits, throws or hangs never takes the caller with it; the
owner of the providers' token cache (`MishkaPay.Helpers.TokenCache`); and the providers
(`plugins/0`), each a mishka_installer plugin it starts itself, as every Mishka CMS package starts
its own.

Which providers start is an option, all of them by default (a provider without a site's keys
answers nothing for that site):

    config :mishka_pay, providers: [MishkaPay.Providers.Stripe]

A provider waits for mishka_installer's registry and registers once it is up: inside Mishka CMS
it always is; elsewhere see `MishkaPay.Registry`.

# `plugins`

```elixir
@spec plugins() :: [module()]
```

The providers chosen (`config :mishka_pay, providers: [...]`), which Mishka CMS reads to check
each package starts its own plugins.

---

*Consult [api-reference.md](api-reference.md) for complete listing*
