How does an out-of-the-box integration make go-live "configuration, not integration"?

For the integrations that are built as plug-ins (payment gateways, the external-delivery model, marketing send providers), going live is configuration, not integration — you typically just enter the provider's credentials (a key/secret) and select it, rather than commissioning a development effort. The heavy lifting is in the platform; you supply the keys. This is the design intent…

For the integrations that are built as plug-ins (payment gateways, the external-delivery model, marketing send providers), going live is configuration, not integration — you typically just enter the provider's credentials (a key/secret) and select it, rather than commissioning a development effort. The heavy lifting is in the platform; you supply the keys. This is the design intent across the plug-in points: adding a provider you're entitled to use should be a settings task an operator can do, not a coding project — which is what "configuration, not integration" means.