Automation Console — Customer Journey Test

Step 1

API connection

Working PoC values are prefilled and remain editable. The token stays in this page only and is never stored.

GET schema

Default merchant selected

FloCash Sandbox prt_flocash_sandbox

Portal URL: https://sandbox.flocash.com/login.do
Merchant account: marocair1@mobirr.com
Password: Stored on server

Default in use

Merchant accounts

The default merchant always remains available when you add another merchant.

1 merchant

FloCash Sandbox prt_flocash_sandbox https://sandbox.flocash.com/login.do · marocair1@mobirr.com

Default · In use

API base URL This public environment uses a secure https:// API URL. Update the prefilled address only when testing another deployment. Portal / workspace Partner bearer token

Auto-poll session

Add another merchant Enter the new merchant details below, then save and use that merchant.

The backend creates a separate merchant ID, partner token, and browser session. The password is cleared from this form immediately after it is saved.

Credentials are sent only to this deployment's HTTPS API and are stored server-side. Use approved test merchant accounts only.

Creation uses the partner bearer token entered above. That token must be authorized by the backend to create merchants.

Configuration

Automation parameters

The fields below are rendered from sections[] and seeded from executionConfig.

Schema not loaded

Load the API schema to render the server-managed portal configuration and report fields.

Steps 3–5

Run the customer journey

Connect opens the Live Browser for CAPTCHA. Export becomes available only when the session is ready.

POST automation