Skip to main content

Testing

Group Payments provides comprehensive sandbox environments for development teams to test their integrations safely. This guide provides the specific test data and procedures needed to validate your onboarding and payment processing implementations.

Sandbox Environment Access​

Your development team will receive sandbox API credentials during project setup, providing access to isolated testing environments that mirror production functionality without processing real transactions or affecting live data.

Customer Onboarding Testing​

Credit Risk Assessment Flow​

When testing the Credit Risk data collection process, customers are redirected to complete required business information fields. Most fields accept standard test data, but specific values are required for certain fields to ensure successful flow completion.

Required Test Bank Account Details​

For testing bank account validation, use these specific test credentials:

  • Sort Code: 108800
  • Account Number: 00012345

All other banking fields can accept valid formatting test data (e.g., realistic bank names, addresses, etc.).

Stripe KYC Validation Flow​

The Stripe sandbox onboarding environment allows testing of the complete KYC verification process with flexible data requirements.

Sandbox Features​

Bypass Options: Stripe's sandbox provides bypass capabilities for certain verification steps including email verification, mobile phone validation, and authentication codes

Test Data Flexibility: Most form fields accept any realistically formatted data for testing purposes

Verification Simulation: The sandbox simulates real verification processes without requiring genuine identification documents

Webhook Testing​

Credit Risk Assessment Approval​

Currently, Credit Risk assessment approval and rejection actions require manual triggering and cannot be automated in the sandbox environment.

Request Process​

To trigger Credit Risk assessment status changes:

  1. Contact Support: Submit a request to Group Payments support specifying the customer ID and desired assessment outcome
  2. Communication Channel: A dedicated support channel will be established at project initiation to expedite these testing requests
  3. Response Time: Manual triggers are typically processed within business hours during active testing phases

Stripe Information Requests​

You can simulate Stripe's request for additional customer information that occurs during live payment processing without blocking transaction capabilities.

Triggering Additional Information Requests​

Use the following Stripe API request to simulate additional information requirements:

curl --location 'https://api.stripe.com/v1/accounts/{CONNECT_ACCOUNT_ID}' \
--header 'Content-Type: application/x-www-form-urlencoded' \
--header 'Authorization: Bearer {STRIPE_SANDBOX_SECRET_KEY}' \
--data-urlencode 'company[tax_id]=111111111'

A successful response will return the following requirement changes.

    ...
    "requirements": {
        "alternatives": [],
        "current_deadline": 1751042055,
        "currently_due": [
            "settings.card_issuing.tos_acceptance.date",
            "settings.card_issuing.tos_acceptance.ip",
            "tos_acceptance.date",
            "tos_acceptance.ip"
        ]
    }
    ...

System Response flow​

  1. Stripe Webhook: Stripe triggers an account.updated webhook to Group Payments
  2. Dashboard Update: The Stripe Platform dashboard shows the account status as "Restricted soon"
  3. Status Update: Group Payments updates the customer status and triggers a webhook to your endpoint
  4. Webhook Payload: Your system receives a status change notification:
    {
    "stripe": {
        "dataCapture": {
            "status": "PENDING"
        }
    }
    }

Customer Notification​

Your application should notify the customer of pending requirements and provide appropriate remediation guidance.

Information Request Remediation​

When customers need to provide additional information to Stripe:

  1. Submit Update Request: Make a PUT /merchants/{id} request to the Merchant API
  2. Response Handling: Extract the redirectUrl from the API response
  3. Customer Redirect: Direct the customer to the provided Stripe URL to complete additional requirements