# Access the app web interface

Learn how to access the web interface for the Stripe App for Oracle Simphony.

After you finish configuring the app, you can access the web interface by doing the following:

1. Open a browser and go to **https://127.0.0.1:8443/dashboard**.
2. Enter your admin username and password. The default username is `admin` and the default password is `admin`. We recommend changing the password for the default admin user and storing it in a secure password vault.
3. Click **Sign In**.

## Manage web interface users 

When you first log in to the [dashboard](https://127.0.0.1:8443/dashboard), you use the default admin user and password. The admin user can change the merchant secret key and create other super admin users, so controlling access to this account is necessary to ensure a secure operating environment.

### Change the password for the default admin user

Navigate to **Account** > **My Account**. Enter a new password and your current password, then click **Save**.

Your new password must meet the following requirements:

- Include at least one numeric character (`0` to `9`).
- Be a minimum of six characters in length.
- Contain at least one lowercase letter.
- Contain at least one uppercase letter.
- Contain at least one non-alphanumeric character (`!@#$%^&*()[]{}<>:;.,~_-+=|\?/"'`).

### Create a super admin user

A super admin user has permission to set merchant private keys and related private read-only information. This user can also configure all user accounts, including merchants and devices.

1. In the [dashboard](https://127.0.0.1:8443/dashboard), click **Settings** > **User Management**.
2. On the User Management page, click **Add New**.
3. On the Add new user page, do the following:
   - Provide the relevant details.
   - Select all permissions for a super admin user.
   - Click **Save**.

### Create a configuration user

A configuration user has permission to add users (except super admins), readers, and workstations, and perform all other non-super admin actions.

1. In the [dashboard](https://127.0.0.1:8443/dashboard), click **Settings** > **User Management**.
2. On the User Management page, click **Add New**.
3. On the Add new user page, do the following:
   - Provide the relevant details.
   - For **Permissions**, deselect **Merchant Management** and **User Management**.
   - Click **Save**.

> Don’t select the following permissions: **Merchant Management** and **User Management**. The secret key gets automatically added for the merchant, and the configuration user can create super admin users.

### Manage logged-in users

Users can manage their account settings or sign out of their account [dashboard](https://127.0.0.1:8443/dashboard), click **Account** and select either **My Account** or **Sign Out**.

## Transactions 

The **Transactions** tab shows a list of transactions with metadata for each transaction where you can search the transaction list. You can sort the **Sequence No.** column by clicking the column header.

| Column Name | Description |
| --- | --- |
| `#` | Transaction number |
| Sequence | Indicator of the order of webhook events |
| Payment Intent ID | A unique identifier used by Stripe to represent the payment intent. This ID allows developers and businesses to track and manage the payment process throughout its lifecycle, including confirmation, cancellation, and refunds. |
| Charge ID | The unique identifier for a successful payment transaction made using a payment method |
| Trans Type | The type of transaction |
| Trans Date | The date of the transaction |
| Actions | Click to view additional details about the transaction |

## Manage Terminal readers 

The **Reader Management** page displays a list of reader devices with the following columns:

- `#`
- Name
- Merchant
- Reader ID
- Workstation ID
- Serial No
- Created By
- Actions

### Add readers to the app

1. On the Reader Management page, click **Add New**.
2. On the Add new reader page, provide the following details, and click **Save**.

| Field | Description | Source |
| --- | --- | --- |
| `#` | Merchant number | Middleware generated |
| Name | The name of the reader | Stripe |
| Merchant | Merchant Name | Merchant |
| Reader ID | The ID of the Stripe reader | Stripe |
| Workstation ID | The ID of the Oracle workstation | Oracle |
| Serial No | The serial number of the Stripe reader | Stripe |
| Created by | User who created the Merchant id |  |
| Actions | Click to view additional details about the reader and update or delete a merchant |  |

### Update or delete a reader

1. On the Reader Management page, locate the reader you want to update or delete.
2. Under **Actions**, select **Edit** or **Delete**.

## Manage merchants 

The Merchant Management page displays a list of merchants with the following columns:

- `#`
- Name
- Merchant ID
- OPI Site ID
- Created By
- Actions

### Add merchants to the app

1. On the Merchant Management page, click **Add New**.
2. On the Add new merchant page, provide the following details, and click **Save**.

| Field | Description | Source |
| --- | --- | --- |
| `#` | Merchant number | Middleware generated |
| Name | The name of the merchant |  |
| Merchant ID | The Stripe account ID in the format `acct_*********` | Stripe |
| OPI Site ID | The Oracle site ID in the format `STRIPE|"site ID"` | Oracle |
| Created by | User who created the Merchant id |  |
| Actions | Click to view additional details about the merchant and update or delete a merchant |  |

### Update or delete a merchant

1. On the Merchant Management page, find the merchant you want to update or delete.
2. Under **Actions**, select **Edit** or **Delete**.

### Configure STS for Pay at Table

If you’re using Pay at Table, configure the Oracle Security Token Service (STS) for each location to allow the app to authenticate with Oracle’s identity provider. Contact Oracle for your STS credentials before completing this step.

1. On the Merchant Management page, locate your merchant and click **Manage STS**.
2. Fill in the following fields and click **Save**.

| Field | Description |
| --- | --- |
| STS Host | The STS server hostname, used for OAuth token requests, identity validation, and TLS handshake |
| Client ID | The OAuth application’s public identifier issued by Oracle IDCS/OHRA. Used to identify the app when requesting tokens. |
| Org Short Name | A short code representing the Oracle organization or tenant |
| STS API Base | The base URL for the Oracle STS API. All token endpoints are built from this base. |
| Loc Ref | Location reference code that maps the merchant to a specific property or location in Oracle Hospitality systems |
| Rvc Ref | Revenue center reference that identifies the revenue center, such as a restaurant, bar, or front desk |
| Tender ID | The tender type identifier used by the POS to classify the payment type, such as credit card, cash, or room charge |
| Username | The username for STS authentication. Required in Oracle environments that use user-based authentication. |
| Password | The password paired with the STS username |
| Merchant Site ID | The Oracle site ID in the format `STRIPE|"site ID"` |