Kartris User Guide

17.20.1. Setup within Kartris

In addition to the general settings most gateways have, Stripe requires these particular ones:

17.20.1.1. ApiKeyPublishable

This is the "publishable" API key that Stripe will generate for you inside your account. This key is used by Kartris when formatting the javascript that forwards user sessions over to Stripe for the payment. It will generally start with the letters "pk_". It is called "publishable" since this is used in client-side code so can be visible to users.

17.20.1.2. ApiKeySecret

This is the key that Kartris uses server-side to communicate with the Stripe servers. This will not be visible to the user's browser in any way during the process, and as such is "secret". It will generally start with the letters "sk_".

17.20.1.3. WebhookEndpointSecret

Webhooks are setup in Stripe to post information back to web sites when certain events happen. In our case, we're interested in getting notification when checkout sessions are completed (i.e. customer completes payment). More detail on setting these up below. But a secret value is used to secure these, and that should be entered here.

 

See @17.20.2. Setup within Stripe‍ for more details.

17.20.1.4. StripeJSSourceURL

A client-side javascript library is used to format javascript to redirect user sessions from Kartris over to Stripe's payment pages. This is the path to that library. In future, Stripe may require we link to newer libraries, hence we have this URL in the settings so it can be changed easily.

17.20.1.5. OrderDescription

For simplicity, we format the order as a single item with a value to send to Stripe. When users checkout, they will see this item on the left of the page with its value. The name shown to users will be [OrderDescription][OrderID]. You can change the OrderDescription part here to customize the order description to your own site's name.

 
powered by tomehost