Expert in Stripe Connect Account (CUSTOM) - backend node.js (express)
Budget: $750 – $1,500 USD
1. Purchese SMS - integrate into react.js (redux saga)
- The one which is going to purchese SMS is Business_id, not Client_id, so the stripe_customer_id must be saved in business table not into client table (in db)
- the business_id details from business profile have to be related to the payment details or at least to have business_id into the payment to know later to whom to create the invoice.
- if business_id (stripe_customer_id) have more then 1 credit card attached, we have to show the option to choose the card which likes to be used for that payment
- Add/edit/delete/set default credit card section have to be into my dasbhaord, not redirect to billing.stripe.com (https://billing.stripe.com/)
2. Get payment_ids via webhook and store in our DB. I think default 21 columns will be enough, no need the 58.
3. Get payouts by webhook and find a way to have the payment_ids into each.
4. Generate invoices:
- Based on payouts, we need to generate invoices. we have 2 ways. a)generate PDF and send to customer email address and via api to the dashboard (for superadmin and to specific business_id). here into the api if we dont specify the business_id, means is for superadmin. if we parse business_id we get all payouts related to
- Based on payments, if SMS, we generate invoices from Tabo to that business_id
- based on payments, we generate invoices from Tabo to that business_id for the fee kept
5. Subscritions (including coupons - all time, due to)
the Invoice page on superadmin will be copied and used into admin dashboard, so they will be able to see the invoices history. from there, they will use the tamplate already made to print the invoices.
Note: the payouts are not mine, the payouts i refer to my Connects
- The one which is going to purchese SMS is Business_id, not Client_id, so the stripe_customer_id must be saved in business table not into client table (in db)
- the business_id details from business profile have to be related to the payment details or at least to have business_id into the payment to know later to whom to create the invoice.
- if business_id (stripe_customer_id) have more then 1 credit card attached, we have to show the option to choose the card which likes to be used for that payment
- Add/edit/delete/set default credit card section have to be into my dasbhaord, not redirect to billing.stripe.com (https://billing.stripe.com/)
2. Get payment_ids via webhook and store in our DB. I think default 21 columns will be enough, no need the 58.
3. Get payouts by webhook and find a way to have the payment_ids into each.
4. Generate invoices:
- Based on payouts, we need to generate invoices. we have 2 ways. a)generate PDF and send to customer email address and via api to the dashboard (for superadmin and to specific business_id). here into the api if we dont specify the business_id, means is for superadmin. if we parse business_id we get all payouts related to
- Based on payments, if SMS, we generate invoices from Tabo to that business_id
- based on payments, we generate invoices from Tabo to that business_id for the fee kept
5. Subscritions (including coupons - all time, due to)
the Invoice page on superadmin will be copied and used into admin dashboard, so they will be able to see the invoices history. from there, they will use the tamplate already made to print the invoices.
Note: the payouts are not mine, the payouts i refer to my Connects