Solve Recaptcha v2 Enterprise
Solves Google reCAPTCHA v2 Enterprise challenges with custom payload support. reCAPTCHA v2 Enterprise is the business/enterprise version of reCAPTCHA v2 with enhanced security features and additional configuration options.
Common Properties
- Name - The custom name of the node.
- Color - The custom color of the node.
- Delay Before (sec) - Waits in seconds before executing the node.
- Delay After (sec) - Waits in seconds after executing node.
- Continue On Error - Automation will continue regardless of any error. The default value is false.
If the ContinueOnError property is true, no error is caught when the project is executed, even if a Catch node is used.
Inputs
- Session - The session ID returned from the Create Session node.
- Website URL - The full URL of the target page where the reCAPTCHA Enterprise appears (e.g.,
https://example.com/enterprise-login). - Website Key - The site key found in the page source. Format:
6Le-wvkSAAAAAPBMRTvw0Q4M....
Options
- Enterprise Payload - Optional custom s parameter for enterprise sites. This is an additional security parameter specific to Enterprise implementations.
- No Cache - Disable result caching for this task. Default is
false. Set totrueto force a fresh solve.
Output
- Token - The g-recaptcha-response token to submit with your form or API request.
How It Works
The Solve Recaptcha v2 Enterprise node solves Google's enterprise-grade reCAPTCHA v2. When executed, it:
- Retrieves the session using the provided session ID
- Creates a reCAPTCHA v2 Enterprise solving task with the website URL and site key
- Optionally adds the enterprise payload if provided
- Sends the task to CapMonster Cloud for processing
- Waits for the challenge to be solved (including image selection if required)
- Returns the g-recaptcha-response token
Requirements
- A valid CapMonster session (from Create Session node)
- The full URL where the reCAPTCHA Enterprise is displayed
- The reCAPTCHA Enterprise site key from the page source
- Sufficient account balance
- Active internet connection
Error Handling
The node will fail in the following cases:
- Missing or invalid session ID
- Session not found
- Empty or invalid website URL
- Empty or invalid site key
- Invalid enterprise payload format
- Insufficient account balance
- Network connectivity issues
- Captcha solving timeout
- Unsupported Enterprise configuration
- Invalid custom parameters
What is reCAPTCHA v2 Enterprise?
reCAPTCHA v2 Enterprise is Google's premium captcha solution offering:
- Enhanced bot detection
- Advanced security features
- Custom security policies
- Detailed analytics and reporting
- SLA guarantees
- Priority support
- Additional configuration options
Finding reCAPTCHA Enterprise Parameters
To find the required parameters, inspect the page source:
Website URL
Use the full URL of the page where the captcha appears:
https://example.com/enterprise-login
Site Key
Look for the Enterprise reCAPTCHA in the HTML:
<div class="g-recaptcha" data-sitekey="6Le-wvkSAAAAAPBMRTvw0Q4Muexq5bi0DJwx_mJ-"></div>
Or in JavaScript with enterprise parameter:
grecaptcha.enterprise.render('recaptcha-container', {
'sitekey': '6Le-wvkSAAAAAPBMRTvw0Q4Muexq5bi0DJwx_mJ-'
});
Enterprise Payload (s parameter)
Look for the s parameter in the page source or API calls:
grecaptcha.enterprise.execute('site-key', {
's': 'enterprise_payload_value_here'
});
Or in the HTML:
<input type="hidden" name="recaptcha-s" value="enterprise_payload_value">
You can also find it in the iframe URL:
https://www.google.com/recaptcha/enterprise/anchor?k=SITEKEY&s=PAYLOAD
Usage Notes
- Enterprise solving typically takes 20-45 seconds
- The response token is valid for approximately 2 minutes
- Use the token immediately after receiving it
- Enterprise implementations may have stricter validation
- The enterprise payload is required by some implementations
- Token format is the same as standard reCAPTCHA v2
- Some enterprise sites have additional security checks
Example: Solving Enterprise reCAPTCHA
Inputs:
- Session: (from Create Session node)
- Website URL:
https://enterprise.example.com/login - Website Key:
6Le-wvkSAAAAAPBMRTvw0Q4Muexq5bi0DJwx_mJ-
Options:
- Enterprise Payload:
s_value_if_required - No Cache: false
Output:
- Token:
"03AGdBq24PBCbwiDRaS9b7T..."
Example: Complete Flow
Create Session (API Key)
→ Browser: Navigate to enterprise page
→ Browser: Fill form fields
→ Extract site key from page
→ Extract s parameter (if present)
→ Solve Recaptcha v2 Enterprise
→ Browser: Execute Script (set token)
→ Browser: Submit form
Submitting the Token
Enterprise reCAPTCHA tokens are submitted the same way as standard v2:
Method 1: Hidden Form Field
document.getElementById('g-recaptcha-response').value = token;
document.querySelector('form').submit();
Method 2: Enterprise API Method
grecaptcha.enterprise.ready(function() {
document.getElementById('g-recaptcha-response').value = token;
submitForm();
});
Method 3: API Request
{
"username": "user@example.com",
"password": "password123",
"g-recaptcha-response": "token_here"
}
Method 4: With Custom Payload
// Set both token and payload if required
document.getElementById('g-recaptcha-response').value = token;
document.getElementById('recaptcha-s').value = enterprisePayload;
document.querySelector('form').submit();
Best Practices
- Always extract the enterprise payload from the page if present
- Verify you're using the correct Enterprise site key
- Test thoroughly as Enterprise implementations vary
- Handle token expiration with retry logic
- Monitor solve times (Enterprise can be slower)
- Use No Cache during development and testing
- Validate the website URL matches exactly
- Store enterprise payload as a variable if it's static
Common Issues and Solutions
Issue: Token rejected with "invalid parameters"
- Solution: Check if enterprise payload is required
- Solution: Verify you're using an Enterprise site key
- Solution: Ensure the Website URL matches the registered domain
- Solution: Try extracting and including the s parameter
Issue: How to identify if it's Enterprise vs standard v2?
- Solution: Look for
grecaptcha.enterprisein the JavaScript - Solution: Check the iframe URL for
/enterprise/path - Solution: Inspect API calls for enterprise-specific parameters
- Solution: Standard v2 uses
grecaptcha.render, Enterprise usesgrecaptcha.enterprise.render
Issue: Cannot find enterprise payload
- Solution: Not all Enterprise implementations require it
- Solution: Try solving without the payload first
- Solution: Inspect network requests for the
sparameter - Solution: Check for hidden form fields with enterprise data
Issue: Higher failure rate than standard v2
- Solution: Enterprise has stricter validation
- Solution: Ensure all parameters are correct
- Solution: Verify the enterprise payload if used
- Solution: Check if additional security features are enabled
Issue: Token expires too quickly
- Solution: Submit the token immediately after receiving it
- Solution: Reduce delays in your automation flow
- Solution: Implement token refresh logic if needed
When to Use Enterprise Payload
The enterprise payload is required when:
- You see the
sparameter in the page source - The reCAPTCHA widget includes
data-sor similar attribute - Standard solving fails with "invalid parameters"
- The site explicitly uses
grecaptcha.enterprise.executewithsparameter - Network inspection shows the
sparameter in requests
Identifying Enterprise vs Standard reCAPTCHA
Enterprise Indicators:
// Enterprise uses .enterprise namespace
grecaptcha.enterprise.render('container', {...});
grecaptcha.enterprise.execute('key', {...});
Standard v2 Indicators:
// Standard uses direct methods
grecaptcha.render('container', {...});
grecaptcha.execute('key', {...});
iframe URL Check:
Enterprise: https://www.google.com/recaptcha/enterprise/anchor?k=...
Standard: https://www.google.com/recaptcha/api2/anchor?k=...
Enterprise vs Standard v2 Differences
| Feature | Standard v2 | Enterprise v2 |
|---|---|---|
| API Endpoint | /api2/ | /enterprise/ |
| JavaScript API | grecaptcha.* | grecaptcha.enterprise.* |
| Custom Payload | No | Yes (s parameter) |
| Analytics | Basic | Advanced |
| SLA | No | Yes |
| Custom Policies | Limited | Extensive |
| Solve Time | 15-40 sec | 20-45 sec |
| Cost | Standard | Higher |
Cost Considerations
- Enterprise reCAPTCHA solving typically costs more than standard v2
- Check CapMonster Cloud pricing for current rates
- Monitor your balance for enterprise-heavy workloads
- Consider caching (No Cache = false) for cost efficiency
- Balance security requirements with budget constraints
Advanced Tips
- Enterprise implementations often use additional JavaScript validation
- Some sites combine Enterprise with custom backend validation
- The enterprise payload may be dynamic or static
- Token validation on the server side is typically stricter
- Always verify the complete integration before production deployment
- Monitor for changes in enterprise payload requirements
- Some enterprise sites use both v2 and v3 simultaneously
- Consider implementing fallback logic for enterprise failures
- Test with different payload values if standard approach fails
- Keep track of successful payload patterns for reuse
Security Considerations
- Enterprise implementations have enhanced bot detection
- More aggressive monitoring of automation patterns
- May use behavioral analysis in addition to captcha
- IP reputation plays a larger role
- Token validation may include additional server-side checks
- Consider using residential proxies for best results
- Implement realistic delays and human-like behavior
- Monitor for any changes in validation requirements
Troubleshooting Checklist
When enterprise solving fails, verify:
- You're using the correct Enterprise site key
- The Website URL exactly matches the implementation
- The enterprise payload is correctly extracted (if required)
- You're calling the enterprise API methods, not standard
- The token is submitted within the validity period
- All form fields required by the site are populated
- Your IP/proxy reputation is acceptable
- CapMonster Cloud service is operational
- Sufficient balance is available
- No additional authentication is required