Step 2: Activate Stripe in Merchant Backend and Create Connection

Prev Next

Preliminary Remarks

In order to link Stripe with the Merchant Backend, certain information is required, which must be copied from the Stripe account and pasted into the Merchant Backend:

  • 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 always recommend performing the stripe setup on the Frisbii Media Stage system first.

To set up Stripe, the data records from the Stripe Backend Sandbox mode must be selected for the Frisbii Media Stage system and the data records 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.


Activate Stripe in the Merchant Backend

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

  • Open the menu item Settings > Financial > Payment Methods.

  • Open the Payment transactions tab.

  • Click on Edit .

  • Select Stripe as PSP in the drop-down list.

Note: This selection cannot be undone. 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.

Now the data records from the Stripe backend are required.    


Data records from the Stripe backend

Stripe Account UniqueID

  • Click on the gear symbol at the top right.

  • Click on Profile.

  • Scroll to the bottom.

  • Under Accounts there is a list in which the ID can be viewed.
    The ID looks like this: acct_xxxxxxxxxx

Publishable key and secret key

  • Click on Developers at the bottom left.

  • Click on the API keys tab.

  • Click on the 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 the Aecret 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 Developers, click on the Webhooks tab.

  • Click on + Add endpoint.

  • Copy the endpoint URL from the Frisbii Media Merchant Backend and paste it into Stripe.

    • URL for the stage system: https://callbacks.plenigo-stage.com/callbacks/v1.0/stripe/companyID    

    • URL for the live system: https://callbacks.plenigo.com/callbacks/v1.0/stripe /companyID

  • Click on + Select events.

  • In the search bar , search for and select the events in the list below. Click on Add events to add the selected events.
    More information about the API events can be found in 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 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).

  • Click on Add endpoint at the bottom when all events have been added.

The webhook was successfully created and will be opened. If all events have been added correctly, there should be 15 events in the "Listening for" column and the Signing secret is in the fourth column.

  • Click on Revealto view and copy the secret key.