PluginVersion 3.0.0

Stripe

Sets up Stripe products, one-time prices and webhook endpoints with a restricted key, and reads checkouts, payments, customers and events.

Download stripe-plugin-3.0.0.zip Source

5.7 MB. Check the download against its SHA-256 below.

What it contains

Settings: Mode, Key vaults, Expected Stripe account
Keys: Restricted API key
Sign-ins: Stripe, Microsoft
Events: A Stripe object was created, updated or removed in apply mode. A command was refused: a secret key, a key for another account, a vault not in keyVaults, or bad arguments; or setup found the key lacks a needed permission, which the reason names.
Skills: plugin-stripe-plugin

Documentation

What it does

Webhook signing secrets go straight into an Azure Key Vault, never into any output. Dry run by default; never moves money.

What it needs

Accounts you connect

Stripe required

an Apikey account

The Stripe account's restricted key (rk_test_... or rk_live_...): an API-key connection with the Stripe preset, added and assigned to this team in Team settings -> Connections. A secret key (sk_...) is refused. Make the key with the permissions the package README lists under "The restricted key's permissions".

Microsoft optional

a Microsoft account

Optional: a Microsoft account with the Contributor or Key Vault Contributor role on the Key Vaults in keyVaults. Used for Azure management only, to write secrets to the Key Vaults in keyVaults.

Keys set on the Host

A plugin names its secret fields; you choose the key each one reads when you hire it.

apiKeyrequired: Moved: from 3.0.0 the restricted key is held by the API-key connection bound to the stripe slot, set in Team settings -> Connections. Declared only so an update carries an existing value over into that connection.

Settings you choose

modeoptional: dryrun looks everything up and says what it would do, and changes nothing in Stripe or Key Vault; setup in dryrun only reads, and checks each listed vault is reached through Azure management. apply makes the changes; setup in apply also writes the check secret stripe-plugin-check to each listed vault to confirm it can be written.
keyVaultsoptional: The Azure Key Vaults a webhook signing secret may be written to, by name, such as payments-vault, or by its address ending in vault.azure.net. The plugin finds each vault in the subscriptions the signed-in Microsoft account can read and writes to it through Azure management. Any other vault is refused. Empty: no webhook secret is written anywhere.
expectedAccountoptional: The Stripe account (acct_...) the key must belong to. setup names it and keeps it for this member; copy it here to make it permanent. Every run refuses a key for any other account.

Setting it up

Accounts you connect

Stripe required

an Apikey account

Microsoft optional

a Microsoft account

Optional: a Microsoft account with the Contributor or Key Vault Contributor role on the Key Vaults in keyVaults. Used for Azure management only, to write secrets to the Key Vaults in keyVaults.

Settings and secrets

Mode optional

Default: dryrun

dryrun looks everything up and says what it would do, and changes nothing in Stripe or Key Vault; setup in dryrun only reads, and checks each listed vault is reached through Azure management. apply makes the changes; setup in apply also writes the check secret stripe-plugin-check to each listed vault to confirm it can be written.

Key vaults optional

No default.

The Azure Key Vaults a webhook signing secret may be written to, by name, such as payments-vault, or by its address ending in vault.azure.net. The plugin finds each vault in the subscriptions the signed-in Microsoft account can read and writes to it through Azure management. Any other vault is refused. Empty: no webhook secret is written anywhere.

Expected Stripe account optional

No default.

The Stripe account (acct_...) the key must belong to. setup names it and keeps it for this member; copy it here to make it permanent. Every run refuses a key for any other account.

Restricted API key secret, optional

Moved: from 3.0.0 the restricted key is held by the API-key connection bound to the stripe slot, set in Team settings -> Connections. Declared only so an update carries an existing value over into that connection.

Entered once per member and kept encrypted; hidden as you type it.

Details

Kind: Plugin
Version: 3.0.0
Plugins: stripe-plugin 3.0.0
Platforms: Linux x64, Linux Arm64
Size: 5.7 MB (5,937,331 bytes)
SHA-256: 8af4acad9065457fbdfc3fd88b91e0cdaf15cf1ad15c039f0b20bfc9b7a6b849
Download: stripe-plugin-3.0.0.zip
Source: github.com/djlsystems/Yawble-packages/tree/main/packages/stripe-plugin
License: Apache License 2.0 (Apache-2.0), separate from the license of Yawble itself

How to install

In Yawble, open Marketplace, find Stripe under Browse and press Get. Or download the .zip, then in Yawble:

Admin
Plugins
Install from a folder

You see what the package adds before it goes in, and you connect its accounts and set its keys afterwards.