FAQ

jetpay integration frequenty asked questions why is my api key not working? the most common reason for an api key failing is that the environment that the key was created in does not match the environment of the endpoint you are calling for example, if the key was generated in the demo/sandbox environment, but the base url of the endpoint you are calling is for the production environment, you will get a 401 unauthorized error double check that these two enivronments are aligned see getting started docid\ homyq3ncmcjvlcuaiosoj if it is your first time integration with the sandbox environment, and it will walk you through the process of setting up an account and getting an api key what are the differences between v0 and v1? functionally, v1 is the same as v0 the main difference is that v1 is structured more intuitively, with some some endpoints being separated for clarity how will we be notified of changes in payment status? currently, polling the api is the only method to fetch the status of a transaction a webhook system is in development for real time notifications, but is not available yet is there rate limiting for api requests? no, there are no rate limits on api requests you can poll the api as frequently as needed without worrying about limitations do we need to worry about pci compliance? all sensitive user information is tokenized on our side and there is no case where you need to store this information yourself, so no card details are ever handled by your server why are there api scopes? we allow you to select api scope(s) to control what each api key has permission to do can we send user credit card details directly to the api? no, you cannot send credit card details directly to the api if a user wishes to pay via credit card, then they will enter card details in our provided ui and handled on our side still confused or blocked? please reach out directly to our team