Stripe Payment Provider Setup

ThisThe Stripe Payment Provider Setup feature showsallows howadministrators to integrate with Stripe to process credit card payments directly within the system. Its primary purpose is to provide a secure and seamless checkout experience for users while simplifying financial reconciliation for your operations. This article is intended for OPSCOMOPS-COM administrators responsible for financial setup.setup and payment gateways.

---

Setup and Configuration

Admin

This Portal

feature

Torequires beginconfiguration within the integration, an administrator must setup a payment type in OPSCOM, with will be linked to their Stripe account. This is handled through the centralOPS-COM administration portal whereas youwell willas inputthe yourexternal uniqueStripe credentials.developer dashboard.

Admin Side: Administrators must have the appropriate system role permissions enabled to access the payments configuration menus and establish external integrations.

User Side: End-users interact with this feature seamlessly during the checkout process on the web portal or when interacting with field staff using handheld devices.

Admin Portal Configuration

1. Hover over System Configuration, >click Payments, then click Setup Payment Types.

2. Click the Add Type. button.

3. Click the Payment Provider drop-down menu and choose StripeStripe.js.js

   from the available options.

Once the provider is selected, you can nameName the payment type,type, select the applicable user types,types, and then go toclick the settingsSettings tab.tab.

Now,

you have to get the API keys for your Stripe account, and setup webhooks, which can be found on the stripe dashboard, which you should be logged into, from a previous step. Your Publishable Key, and Secret Key, can be found and copied here. You can click on these values to copy them, and paste them into the payment type settings in OPSCOM.

You must provide your unique identification keys. Enter your Stripe public key into the Publishable Key fieldfield.

and

Enter your Stripe secret key into the Secret Key field.

Verify that the Currency setting is correct for your region (the default is US dollars).

Only enter testing credentials into the Testingconfiguration Credentialsfields until you are completely ready for your users to have live access to this.

Take this time to ensure that the Currency setting is correct, in the payment typemethod.

settings (the default is US dollars). The next steps will be about populating the Webhook ID and Webhook Secret fields, in OPSCOM, with the correct information from your

Stripe dashboard.

Web

---

Third-Party Webhookhook Configuration

Webhooks are absolutely essential for Stripe to notify OPSCOMOPS-COM regarding payment successes or refund completions.

Without these Webhooks,webhooks correctly configured, the system WILLwill NOTnot communicate any transaction information to OPSCOM.

OPS-COM.

Register Your Endpoint

To begin receiving notifications, you must define exactly where Stripe should send the transaction data.

In

1. Navigate to your Stripe Dashboard, click on Developers (bottom left), and select Webhooks.

   

2. Click the Add Destination button to open the configuration window.

3. You must selectSelect the specific event types the system needs to process.process For a standard setup, ensure you select (payment_intent.succeeded for successful payments,, payment_intent.payment_failed for failed payments,, and payment_intent.canceled for canceled payments. Now click Continue.).

4. Click the Continue button.

5.  Select Webhook endpoint, and click continuethe again.Continue button.

   

6. Give the webhookEnter a descriptive name,name and infor the Endpointwebhook.

   URL
field,
7. enter

   Enter the specific URL provided by OPSCOM,OPS-COM ininto thisthe format:Endpoint URL field (e.g., https://[CLIENTID].ops-com.com/api/system/payments/stripe/callback).

Retrieve Your Signing Secret

Once the endpoint is created, Stripe generates a unique security key to verify that the data sent to your server is authentic.

On

1. Locate the Signing secret section on the summary page for your newly created webhook,webhook.

   locate

2. Click the Signing secretReveal section.

   

   Click Revealbutton to display the string,string (which typically begins with the prefix whsec_whsec_).

3. Copy (highlighted in a green box in the picture above!) this entire string and navigate back to your OPSCOMOPS-COM Payment Gatewaypayment settings.

4. Paste the copied secret into the Webhook Secret field. This handshake ensures that OPSCOM only processes legitimate requests from Stripe and ignores any unauthorized attempts to alter transaction data.

5. OnceCopy the endpoint is saved, you'll see the Signing secret, and Destination ID provided by Stripe.Stripe.

   Return
to
6. your OPSCOM configuration and paste

   Paste the Signing secretID into the Webhook Secret field, and the Destination ID into the Webhook ID field to ensure all incoming data is securely verified.

Ensure that your Webhook Secret is correctly matched between Stripe and OPSCOMOPS-COM to prevent "Pending"pending status errors on completed payments.

Using this Feature

The

---

checkout

Userprocess Experienceis optimized for both web portal users and Handheldadministrators Use

using handheld devices in the field.

Web Portal Transactions

1. UsersClick willthe interactPay with theCredit StripeCard interfacebutton duringwhen their standard checkout process. When theyyou reach the final stage of a transaction, they simply click the Pay with Credit Card buttontransaction to open the secure payment form.

   After
they
2. enter

   Enter the required credit card details intointo the form,form.

   they
click

3. Click the Submit Payment button to complete the purchase.

Handheld App — OPSCOM Parking EnforcementTransactions

1. For administrators or staff using handheld units in the field, the process is optimized for touch interaction. Tap Checkout to open the payment summary within the OPS-COM for Android app.

   From
there,
2. tap

   Tap Select Payment Method and choose Stripe.

   To
prevent
3. accidental charges, the final step requires you to tap

   Tap and holdHold the Process Payment button to finalize the transaction.

Managing Transactions and Reports

Administrators can seamlessly review all processed payments and manage financial returns through the standard reporting interfaces.

1. Hover over Financial Management and, click Transaction Reports, then Recent Payments to view a live list of activity..

2. Within this report,Review the Status column displaysto determine the current state of each payment, whileand the Payment Date indicatescolumn to see exactly when the transaction occurred.

   If
you
3. need more detail, click

   Click the View Details icon next to a specific transaction to see the full Stripe receipt.

4. If a correction is needed, clickClick the Refund Payment button to initiate a return of funds.

   You
will
5. then click

   Click the Confirm Refund drop-down menu and choose Full Refund to finalize the reversal.

   You

can quickly find a specific transaction by using the search bar to enter a user's name or a specific receipt order ID/Confirm Code.

---

Best Practices and Considerations

• DeploymentPerform Testingthorough deployment testing: Organizations should always keep Live Mode disabled during the initial deployment until all testing is verified with test credit card information. It is highly recommended to process a single, small test transaction in Live Mode using a real card before making the payment option available to the general public.

• SecurityMaintain Requirementsstrict security requirements: Maintaining the security of your financial environment is critical. You should never share your Stripe Secretsecret Keykey or Webhookwebhook Secretsecret with anyoneanyone, ornor should you store it in plain text outside of the secure administration configuration screens.

• Rotate security keys regularly: Change the signing secret periodicallyperiodically., andAdditionally, ensure you only subscribe to the strictly required event types.types within Stripe to minimize unnecessary data transmission.