Capstone sets up a ministry’s Stripe, PayPal, shipping, tax, AI and Bible access, which means typing their secrets into a console that is not theirs. Every one of those panels is built the same way so that the console never becomes a place worth breaking into.
Type the key into the panel.
The box always starts blank, even when a key is already set.
Save, and the key is handed straight up to the worker.
It is not written to Capstone’s own records on the way past.
The worker checks it with the vendor before anything is saved.
A wrong key is refused at this point rather than stored and discovered later by a customer whose payment failed.
It is locked away in the ministry’s own Google project, not in Capstone’s.
In a vault Google provides for exactly this — their apps can read it, and nobody browsing Capstone can.
A blank box does not mean no key. It means the box is blank — the panel says separately whether one is set. Leaving it blank and saving keeps the key it has.
Because nothing is kept here, a key cannot be read back out of Capstone. If a ministry loses its own copy, it has to be reissued by the vendor.