Step 2: Activate Stripe in Merchant Backend and Create Connection

    Content of this article

    1. Preliminary Remarks
    2. Activate Stripe in the Merchant Backend
    3. Data Sets from Stripe Backend
      a) Stripe Account Unique ID
      b) Veröffentlichbarer Schlüssel und Geheimschlüssel
      c) Webhook und Geheimschlüssel für Signatur

    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 sets for the Frisbii Media Stage and Live systems. We recommend that you always set up Stripe on the Frisbii Media Stage system first.

    To set up Stripe, the data sets from the Stripe Backend Sandbox mode must be selected for the Frisbii Media Stage system and the data sets from the Stripe Backend Live mode must be selected for the Frisbii Media Live system.

    Sandbox mode is indicated by a dark blue banner at the top of the interface.

    2. Activate Stripe in Merchant Backend

    Stripe must be selected as a PSP in order to set it up in the Frisbii Media Merchant backend.

    • Open Settings > Financial > Payment Methods.
    • Open Payment transactions tab.
    • Click on Edit.
    • Select Stripe as PSP using the drop-down menu.

      Note: This selection cannot be reversed. Only one payment service provider can be used at a time. If you want to change the PSP, please contact the Frisbii Media support team.

    • After saving, the Stripe tab appears, in which the previously compiled data records must be entered.

    Nun werden die Datensätze aus dem Stripe Backend benötigt. 

    3. Data Set from the Stripe Backend

    Stripe Account UniqueID

    • Click on the gear symbol on the right-hand side.
    • Click on Profile.
    • Scroll to the very bottom.
    • Under Accounts there is a list in which you will find the ID.
      The ID looks as follows:  acct_xxxxxxxx


    Publishable key and Secret key

    • Click on Developers in the bottom left-hand corner.
    • Click on API keys tab.
    • Click on Publishable key to copy it.
      • for the Frisbii Media stage system: pk_test_xx
      • for the Frisbii Media live system: pk_live_xx
    • Click on Secret key to copy it.
      • for the Frisbii Media stage system: sk_test_xx
      • for the Frisbii Media live system: sk_live_xx

    Webhook and Signing secret

    • In the search bar, search for and select the events in the list below. Click on Add events to add the selected events.

      For more information on the API events, please 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 successfully been executed.

    payment_method.automatically_updated

    Payment method has automatically been updated

    charge.dispute.closed

    Payment disupute is closed and status changes to “lost”, “warning_closed” oder “won”.

    charge.dispute.created

    Payment dispute has bene 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).

    • Click on Add endpoint as soon as all events have been added.

    The webhook has been successfully created and is opened. If all events have been added correctly, there should be 15 events in the “Listening for” column.

    The secret key for the signature is in the fourth column.

    • Click on Reveal to see the signing secret and copy it.


    Published