Skip to content
Create account or Sign in
The Stripe Docs logo
/
Ask AI
Create accountSign in
Get started
Payments
Revenue
Platforms and marketplaces
Money management
Developer resources
APIs & SDKsHelp
Overview
Versioning
Changelog
Upgrade your API version
Upgrade your SDK version
Essentials
SDKs
API
Testing
Stripe CLI
Sample projects
Tools
Stripe Dashboard
Workbench
Developers Dashboard
Stripe Shell
Stripe for Visual Studio Code
Features
Workflows
Event destinations
Stripe health alertsFile uploads
AI solutions
Agent toolkit
Model Context ProtocolBuild agentic AI SaaS Billing workflows
Security and privacy
Security
Stripebot web crawler
Privacy
Extend Stripe
Build Stripe apps
Use apps from Stripe
    Overview
    Stripe-built apps
    Adobe Commerce
    Cegid
    Commercetools
    Guidewire
    Mirakl
    NetSuite
    Oracle Opera
    Oracle Simphony
      Install the app
      Configure the app
      Access the web interface
    Oracle Xstore
    PrestaShop
    Salesforce
    SAP
    Shopware 6
    Stripe Tax for BigCommerce
    Stripe Tax for WooCommerce
    Partner apps
    Build your own app
Partners
Partner ecosystem
Partner certification
United States
English (United States)
HomeDeveloper resourcesUse apps from StripeOracle Simphony

Configure the app

Learn how to configure the app for Oracle Simphony, including best practices and customization.

After you install the Stripe app for Oracle Simphony, you can configure the settings to use the app with your Stripe Terminal integration.

Configure Simphony

  1. Sign in to the Simphony Enterprise Management Console (EMC) with your administrator credentials.
  2. In the Enterprise menu, select the enterprise that’s going to use the app.
  3. Open the Setup tab to display hardware and interface options.
  4. Go to Hardware/Interfaces > Interfaces, and select Payment Drivers.
  5. Double-click the SPI payment driver to edit its settings.
  6. In the SPI driver window, select the Configuration tab.
  7. Locate the Primary Host field and enter the app host and port (the default is https://localhost:8443/). If you’re installing the app on the CAP server where SPI runs, use Windows File Explorer to go to the installation path, then edit the application.yaml file and update the IP address to the CAP server’s address. Update the Primary Host field here to the CAP server’s IP address also.
  8. Save your changes.

Configure the app

Use Windows File Explorer to go to the installation path and edit the application.yaml file to configure the following app parameters.

Spring MVC
  • spring.mvc.async.request-timeout: The maximum time (in milliseconds) that the server waits for asynchronous web requests to complete before timing out.
  • The default in this app: 120000 (120 seconds).
Server
  • Server.address: Network interface IP address the embedded server binds to.
  • 127.0.0.1 means the application only accepts connections from the local machine.
  • server.port: TCP port the HTTPS server listens on.
Server SSL
  • server.ssl.key-store: Path to the keystore file containing the server’s TLS/SSL certificate and private key. Uses the ${SECURITY_DIR} environment variable and expects a .pfx file.
  • server.ssl.key-store-password: Password used to unlock the keystore file.
  • server.ssl.key-store-type: Format/type of the keystore used by the server.
  • Supported values are:
    • PKCS12: PKCS#12 keystore (recommended and the default when the file has a .p12 or .pfx extension)
  • JKS: Java KeyStore (legacy Java-specific keystore and default when the file has a .jks extension).
    • If not set explicitly, infers the type from the keystore file extension.
  • server.ssl.key-alias: Alias or name of the specific key pair within the keystore that the HTTPS server certificate will use.
Debugging
  • debug: Enables or disables Spring Boot debug mode
    • When false, only standard logging is enabled.
Logging
  • logging.level.com.stripe.opiconnector: Log level for the com.stripe.opiconnector package (app business logic and payment processing)
  • Supported SLF4J/Spring Boot log levels are:
    • TRACE: most detailed logs
    • DEBUG: detailed debug logs
    • INFO: general information logs
    • WARN: warning messages only
    • ERROR: error messages only
    • OFF: no logs.
Was this page helpful?
YesNo
  • Need help? Contact Support.
  • Check out our changelog.
  • Questions? Contact Sales.
  • LLM? Read llms.txt.
  • Powered by Markdoc