1. Are the API endpoints different in production?
No. All API URLs are the same for both test and production accounts. There is no separate production host.
Continue using:
https://svc.claim.md
The existing API service paths also remain the same.
2. Is the AccountKey passed differently in production?
No. The AccountKey is passed the same way using the AccountKey form field, and the account key format remains unchanged.
The only required change is to replace the test account API key with the production API key.
An administrative user can generate the production API key from Settings > Account Settings. API key generation should be immediate after the administrator verifies their password.
Reference: Account Settings
3. What needs to be completed for payer enrollments in production?
The full enrollment process must be completed within the production account for each applicable provider, payer, and transaction type. This includes provider validation when required.
Enrollments completed in the test account do not carry over to the production account.
References:
4. Are payer IDs the same between test and production?
Yes. Payer IDs are the same between test and production accounts. You do not need to use a different set of payer IDs after moving to production.
5. Does the enrollment webhook need to be registered again for production?
Yes. The enrollment webhook must be configured separately for the production account.
Submit a new support ticket from the production account and include the webhook URL you want registered for enrollment status updates.
Summary
From an API connection perspective, the required change when moving from test to production is to replace the test API key with the production API key.
API endpoints, service paths, the AccountKey form field, and payer IDs remain the same. However, payer enrollments and enrollment webhook configuration must be completed separately within the production account.