Skip to main content
The Flinks Guaranteed EFT Sandbox is a test environment designed to validate both back-end and front-end functionalities of the GEFT product.

Overview

The sandbox environment:
  • Does not connect to real accounts or move actual funds
  • Simulates production environment to help test various scenarios
  • Prepares your integration and ensures readiness for go-live
  • Does not replace testing with real accounts and transactions before deployment
The sandbox has two primary purposes:
  1. Test session creation and different user scenarios, and integrate accordingly
  2. Review front-end design and configuration, ensuring they align with your expectations

Base Testing Flow

During testing, follow this sequence:
  1. Authenticate with sandbox using your secret credentials
  2. Initiate session using test scenario name and desired dynamic parameters
  3. Launch iFrame with Session ID appended to trigger front-end scenario
  4. Complete front-end flow by entering specified username/password for that scenario
    • “Happy” paths will return a SUCCESS JS event
    • “Unhappy” paths will display relevant error screen or event
  5. Check session status by calling /sessions/status endpoint
You can perform any front-end actions during testing. Each test user dynamically supports both successful and failed outcomes, reflected in the session’s back-end status.

Sandbox Environment Access

Your sandbox credentials and base URI will be provided during onboarding. The sandbox environment includes:
  • API Endpoints: Same as production but with test data
  • Dashboard Access: Client dashboard instance for UI familiarization
  • Test Data: Predefined scenarios with known outcomes
  • Event Simulation: Full event flow testing capabilities

Authentication

Use your sandbox credentials exactly as you would in production:
  1. Include your API key in the x-api-key header and your client ID in the x-client-id header
  2. Use these headers for all API calls during testing

Next Steps

Once you understand the sandbox basics:
  1. Test Scenarios: Learn about specific test cases and user flows
  2. Testing Best Practices: Implement automated testing
  3. Production Readiness: Verify you’re ready to go live