What problems? Please specify so that we can improve.
There is. As of now it is undocumented, but if you had just reached out to us, we’d have responded. You can enable sandbox mode by setting the ic_api_sandbox_mode site config to 1. You can run the following command to achieve this:
I changed the mode to sandbox, but where can I set the sandbox credentials and which are the sandbox GSTINs which I can use.
What problems? Please specify so that we can improve.
I understand that there is more that I have to explore once I setup the configuration. Probably that will resolve the issues.
This is a wonderful solution that you guys are putting together if everything works out of the box. But it would always be good to provide an option to choose a custom GSP.
You don’t have to worry about these things! They are handled in the source code for e-Waybill and e-Invoice. (example)
All you need to do is login to your India Compliance account and set the ic_api_sandbox_mode config and any dummy credentials. (API credits will not be consumed for sandbox API)
For the Public API (search), you can use this GSTIN: 33GSPTN9771G3ZP
Reasons why we went with our own ASP solution (based on our experience):
GSPs charge separately for different APIs.
GSPs don’t extend validity of API credits about to expire.
Different GSPs sometimes provide APIs differently - there’s no consistency.
The minimum purchase price set by GSPs is generally high for a SME business.
What will the added benefit be, for the end user? All functionality stays the same.
All in all, we wanted to provide a better, consistent UX for the end user.
If you’re a service provider, we provide an option to club the India Compliance API with your service. Frappe already uses this. Additionally, we do offer a post-paid option with a minimum annual commitment. This way, you never have to worry about the expiry of credits.
If you want to hide the India Compliance account from your customers, you can just set the API secret programatically by running following command: