This is the first task for the finance emulator project.
Make sure you know what markdown is: Quickstart for writing on GitHub - GitHub Docs => There is no need to spend a lot of time on it, just know it exists! 🙂
Set a repo README, with description of the project
Let’s define technologies stack
POC = Proof of concept
As software engineer, you first validate if an idea / api integration / logic works.
Then, you worry about making the UI nice, and improve error handling.
Goal guided
Our focus timeframe is limited. Make sure you sit in your laptop knowing what you want to achieve it, and how you will validate it!
On load of this page (which will be the default landing page), you will have 1 button, to connect with STRIPE!
Stripe sign-up
Create an account with stripe
Obtain your API secret keys
Stripe dive-in => You can split each api integration in MULTIPLE sessions, just focus on the single target, and get it :)
Your balance from stripe must consider: expenses, income, refunded income, platform expenses, and you have to distinguish between one time payment and recurring payment.
I suggest you to focus on the curing payment (as most of the business now moves into a membership based model).
Ideally, you want in order:
Get access to these information, and/or being able to extract them as csv/excelt, file.
Or just get the raw number and calculate them ;)
Income:
To retrieve information related to your income, you can use the following API:
Balance Transactions:
Retrieve details about balance transactions, including successful charges, payouts, and other financial events.
Endpoint: GET /v1/balance_transactions/:id
Expenses:
For expense-related data, consider the following:
Application Fees:
Retrieve details about application fees collected on top of charges made for your users (using Connect).
Endpoint: GET /v1/application_fees/:id
Learn more about application fees.
Platform Taxes:
To get information about platform taxes, you can use the following:
Tax Transactions:
Retrieve details about tax transactions associated with your account.
Endpoint: GET /v1/tax/transactions/:id
Refunded Income:
For refunded income, consider the following:
Refunds:
Retrieve details about refunds issued for charges.
Endpoint: GET /v1/refunds/:id
This is the first task for the finance emulator project.
Make sure you know what markdown is: Quickstart for writing on GitHub - GitHub Docs => There is no need to spend a lot of time on it, just know it exists! 🙂 Set a repo README, with description of the project Let’s define technologies stack
POC = Proof of concept As software engineer, you first validate if an idea / api integration / logic works. Then, you worry about making the UI nice, and improve error handling.
Goal guided Our focus timeframe is limited. Make sure you sit in your laptop knowing what you want to achieve it, and how you will validate it!
Gitflow Read about: Quickstart for writing on GitHub - GitHub Docs Make sure you are ALWAYS using PULL requests, and never just push into github.
Repository best practises Set bug and pull request template About issue and pull request templates - GitHub Docs
Pull request example:
backend stack define
Did you define a backend with davide? GOOD! For this session, make 1 view / endpoint, to expose just the landing page.
In django this is called url In Nodejs, route Express Tutorial Part 4: Routes and controllers - Learn web development | MDN (mozilla.org)
On load of this page (which will be the default landing page), you will have 1 button, to connect with STRIPE!
Stripe sign-up
Create an account with stripe Obtain your API secret keys
Stripe dive-in => You can split each api integration in MULTIPLE sessions, just focus on the single target, and get it :)
Your balance from stripe must consider: expenses, income, refunded income, platform expenses, and you have to distinguish between one time payment and recurring payment. I suggest you to focus on the curing payment (as most of the business now moves into a membership based model).
Ideally, you want in order:
Income: To retrieve information related to your income, you can use the following API: Balance Transactions: Retrieve details about balance transactions, including successful charges, payouts, and other financial events. Endpoint: GET /v1/balance_transactions/:id Expenses: For expense-related data, consider the following: Application Fees: Retrieve details about application fees collected on top of charges made for your users (using Connect). Endpoint: GET /v1/application_fees/:id Learn more about application fees. Platform Taxes: To get information about platform taxes, you can use the following: Tax Transactions: Retrieve details about tax transactions associated with your account. Endpoint: GET /v1/tax/transactions/:id Refunded Income: For refunded income, consider the following: Refunds: Retrieve details about refunds issued for charges. Endpoint: GET /v1/refunds/:id