I have some questions...

[andrewdwallo]

If I was going to try to use Plaid with Laravel Models, Migration Tables, etc. How would I go about using your package so that I can receive requests and render responses with plaid? I also wanted to know... How would I go about using your package with Plaid Link where a user can login with something like Jetstream and click on a button to use link and have all of their data come in through the user interface in tables for Models..? I am also planning on using Filament Admin for this... Sorry for all the questions but I am having a hard time trying to do this with Plaid and I am having a lot of errors in doing so... Also, does your package not provide a config file to publish so that I can retrieve your vendor files for models and such in the root folder? Maybe I am just a noob or something but how do I actually go about using your package... I would really appreciate your help, thanks!

[abivia]

Hi @andrewdwallo, thanks for your question!
There are no models. This is simply an interface to the Plaid API. The only configuration is the environment settings described at https://github.com/abivia/plaid#usage

For an example on how to use the interface, check out tests/Feature/TransactionTest.php It shows the process of obtaining an access token and then performing a call to Plaid's transactions/get entry point. The result is an array as described in the Plaid documentation at https://plaid.com/docs/

How your application handles that information, including storing it in your Models is entirely up to you.

[abivia]

And what do you mean by "interface"?

I'm referring to PHP interfaces: https://www.php.net/manual/en/language.oop5.interfaces.php

Much of the Cogs interfaces are based on open standards from OASIS, which is indicative of how I'm trying to structure things. For example there is a European standard for describing product catalogues that I'd like to map as closely as possible to, in hopes of facilitating better API interoperability.

I will see if I can get this thing in shape for a private repo and share it with you. There is currently much code that's specific to our environment that I'd rather not disclose in a public repo just yet.

[abivia]

We have similar goals but I'm not sure if they align 100%. Right now our focus is on meeting some of our critical business requirements.

The good news is that there is an opportunity to collaborate since Ledger covers almost all of what you want in the core accounting module: a double entry ledger and journal, with multiple currencies, sub-journals, and a trial balance, mappings for tax reporting, audit trails, and a statement generator. Missing functionality still includes proper period closing and likely a few other small things I haven't discovered yet.

Nevertheless, Abivia\Ledger was designed exactly for projects like yours. So many developers cobble together code that has accounting functionality without understanding the most basic principles of accounting that I've tried to give them an easy to use base that plugs in and won't cause their CFO to have an aneurysm. I'd be happy to work with you to make it a fully functional core upon which you (and hopefully others) can build their own solutions from club memberships to full ERP solutions.

[andrewdwallo]

Sounds great to me, how could I contact you? Do you have discord or something similar?

[abivia]

I've mostly been using Slack but now that it's Salesforce I'm looking at migrating. Give me a little time to figure out how to move forward and drop info in the repo I just invited you to (you should get it by email).

[abivia]

Sounds great to me, how could I contact you? Do you have discord or something similar?

I've set up a Mattermost cloud instance. If you get your email to me I'll send you an invite You can DM Abivia on Twitter or post in the private repo.