Stripe Data Records to connect to plenigo

Content of this article

  1. Preliminary remarks
  2. Data Records for the Connection

1. Preliminary remarks

To be able to connect Stripe to the plenigo Merchant Backend, specific data is required which are to be copied from the Stripe account and inserted in the plenigo Merchant Backend.
The following data is required:
  • Stripe Account UniqueID
  • Publishable key
  • Secret key
  • Webhook 
  • Signing secret

Note: There are two different data records for the plenigo stage and live systems. We recommend to set up Stripe for the plenigo Stage system first. 

To set up Stripe, the data records from the Stripe backend test mode must be selected for the plenigo stage system and the data records from the Stripe backend live mode must be selected for the plenigo live system. In the Stripe backend, you can switch between test and live mode using the slider at the top right of the interface. If the slider is orange, you are in test mode; if it is gray, you are in live mode.


2. Data Sets for the Connection

Stripe Account UniqueID

  • Click on the gear symbol in the right hand corner.
  • Click on Profile.

  • Scroll to the very bottom of the page.
  • In the list under Accounts in which the ID can be viewed.
    The ID looks as follows: acct_1Orl9EJ3ssjaD4558

Publishable key and Secret key

  • Click on Developer in the right hand corner.
  • Click on API keys tab.
  • Click on Publishable Key to copy it.
    • for the plenigo stage system: pk_test_xx
    • for the plenigo live system: pk_live_xx
  • Click on Reveal test/live key to copy it.
    • for the plenigo stage system: sk_test_xx
    • for the plenigo live system: sk_live_xx

Webhook and Signing secret

  • Click on + Select events.
  • In the search bar, search for and select the events from the list below. Click on Add events to add the marked events. More information about the API events, refer to the Stripe documentation.

Stripe API Event

Meaning

account.updated

An account status or property has changed.

issuing_card.updated

Stored credit card has been updated.

issuing_cardholder.updated

Credit card owner has been updated.

payment_intent.amount_capturable_updated                                                                               

Information on amount of intended payment

payment_intent.canceled

Payment intent has been canceled.

payment_intent.created

Payment intent has been created.

payment_intent.payment_failed

Payment intent has failed.

payment_intent.processing

Payment intent is in process

payment_intent.succeeded

Payment intent has sucessfully been executed.

payment_method.automatically_updated

Payment method has automatically been updated.

charge.dispute.closed

Payment dispute is closed and status status changes to “lost”, “warning_closed” or “won”.

charge.dispute.created

Payment dispute has been initiated with the bank.

charge.dispute.funds_reinstated

Amount has been credited to your account after the payment dispute was completed in your favor (also applies to partially refunded payments).

charge.dispute.funds_withdrawn

Amount has been withdrawn from your account due to payment dispute.

charge.dispute.updated

Payment dispute has been updated (usually with evidence).

  • At the very bottom, click on Add endpoint to create the webhook.
The webhook has been sucessfully created and is opened.
The signing secret can be found below the webhook.
  • Click on Reveal to view the signing secret.