Cart / Payment Gateway Integrations

It would seem there's nothing out there so it's all custom done?

Ok. 

I take it zero replies because everyone views everyone else as a competitor?

I can understand the competitive nature of things.  I'm just looking for some starter info or even a simple sample would be nice for setting up a new user/account.  I've looked through the current SDK and it's very dis-jointed and difficult to follow.  Especially with the comments all inline with the code in the small sandbox area.  I'm not a web dev but I will learn.  I do more of the back end dev and by trade a Unix Engineer but I'll learn the dev as needed. 

Funny, I'm not even in the Fleet tracking arena... not even close.

simplextech, basically to create an account you need login and create session. To login you need token. Please ask token for the user that either is top-level account or has dealer rights, so that you may play with it correctly.

Having active session you may operate using its sid, listen for updates, etc and you may manage some items.

To manage accounts you need to create user, using it's ID create resource and then upgrade it into account.

To block/unblock or perform payments over accounts please look here.

Very basic.  I get an Error 6 - Unknown error.  I'm reading through the documentation and the issue is with the dataFlags it seems.  I've tried several variants and nothing is working.

Anyone have any more information about the quirks of the API or should I not be trying to use the PHP and use something else?

 echo $wialon_api->core_create_user('{
                        "creatorId":18125092,
                        "name":"sdk_test",
                        "password":"sdk_test_123",
                        "dataFlags":1}');

simplextech, congrats on partial success. The best way to check what to do is to use cms.wialon.com and see actual requests and their paramers in browser console.
API docs a little bit outdated and other libraries even much more outdated. The best source of information so far is this forum and people here.

Per your other post:
To manage accounts you need to create user, using it's ID create resource and then upgrade it into account.

This is where the use of "User" for the terminology is misleading and confusing.  Especially for me coming from other systems where a user is a user.  But from the way the system is structured from CMS it's a 3 step process.  Please correct me if I have misread any of this.

1. create user
2. create resource from user id of step 1
3. create account from resource id of step 2 and assign billing plan

The user in step 1 is the "Master User" that the "Account" is comprised of.  Essentially the Login Name for the Account.  Is this not correct?  I don't know of any other way to "Create an Account".

btw, PayPal payments are not 100% covered by WebHooks. In October we had one payment for which PayPal didn't generated the WebHook at all according to WebHook Logs. It means that either you will need some manual activation of your script or still need to run periodic synchronization to be 100% sure. Just for your information.

Are there any issues in Wialon using a "email address" format for the user/resource/account name?  So far it seems to work fine and login and everything is working.  I want to make sure there's no hidden problems I'm not aware of.

What would be the best approach of managing unit number restrictions?  I see that there looks to be a way to change/edit the billing plan to change the service unit value.  Is that the recommended approach for increase/decrease of the the unit limit?

https://sdk.wialon.com/wiki/en/sidebar/ … ng_service

So far things have come along very well.

Integration using Stripe for Billing aka Subscriptions.  I've now integrated with Pabbly for a very easy customer portal and in-between integration with Stripe.

-- Account Create / Delete
-- Service Upgrade / Downgrade

I'm using billing plans at set unit counts to make it easy to change unit plans and automate the process.  Other increments can be done through a support channel.  Almost ready to go live with this and now I've hit a problem.

I've been running on a Wialon trial and things were fine and so we bit the bullet and are now paid customers.  I'm trying to move the integrations from the "test" environment to the new "prod" environment and this should be a simple change of the Token and the CreatorId that is used.  However the exact same code is no longer working in the new environment but it still works perfect in the "trial" environment.  The ONLY difference is the access token and the "CreatorId" used. 

I've sent an email to support.  Waiting on a response.  I think my account my be "broke" in some way as it took several days and escalations to HQ before I could even access my account.  So things were rough from the start.

Any ideas thoughts on other differences I may be over looking?  A permission difference or something?

Well.  The several replies from "Support" were "We don't support the API" and to use the forum. 

So I started over.  Deleted the access from within the CMS for applications with access and created a new token again and started testing and now it's working.  So either I missed something the first three times last night or something changed somewhere.  I don't know.  But as of right now it is working and I can move forward.  I did document this as well and I'll test the steps again with another user to verify them again. 

There is a error code 6 that according to the documentation states "Unknown".  That is NOT helpful and something needs to be done about that.