Developer for billing software
- or -
Post a project like this$$
- Posted:
- Proposals: 9
- Remote
- #2044735
- Expired
Ranked Top 5 CERT in PPH with Microsoft GOLD partner | .NET Framework | Umbraco | PHP/WordPress | Native & Cross Platform Mobile App | MEAN | MERN
Ahmedabad
AI & Data Science Engineer | Nodejs | Ruby On Rails | AWS | GCP | Python | React | Angular |
Auckland
Customized Mobile apps | Website Design & Development | Digital Marketing |E-commerce Solutions
Ahmedabad
1331683367825040918841649280071088681124641316016092186029
Description
Experience Level: Intermediate
The Goal: To create an easier-to-deal-with system that will allow Sales Reps to send unique proposals to users with an option to pay the total amount to include assignment of recurring payments.
I'm still waiting to see if we can work out a way to pay your Sales Reps while still using "Better Proposals" but here is my recommendation with the plan of abandoning "Better Proposals" programming and building your functionality with a Developer.
--Accepting Payments from Customers
Since you would like to create a proposal with a way to pay inside, the way I see it you have two options:
Option 1:
Your development team will need to build a user interface for your Sales reps to be able to create this proposal, and assign the subscription plans that are appropriate for this customer. Through your programming your developers can link these plans to the back end subscriptions to ensure that the charge API (through the Gateway) will automatically assign the right plan when the card is charged.
https://stripe.com/docs/subscriptions/quickstart
The proposal should also be built with one of our Gateways** (to collect the customer's payment information in a PCI compliant way) and populate the appropriate subscription API necessary for what the proposal deems.
This will be the most efficient and automatically generated option. Higher in development time/costs, but less hassle to complete by Sales Reps.
Option 2:
Your proposals can have the breakdown of what they are paying for and when, and your developer can include one of our Gateways** but in this case you wouldn't charge anything right away. Your developer would merely integrate the Gateway to collect and store the customer's payment information as an Object ID (and active "Customer" with saved payment information).
https://stripe.com/docs/saving-cards
The the Sales Rep would then log into your Stripe Dashboard (you can give them their own credentials with limited access and control) and access that "Customer" (once their payment Object ID is saved). They can then tweak their subscription to add payment plan amounts and timing.
This method would be less in development costs, but more overall work for the Sales Reps.
--Needing A Developer
Integrating our API requires at least a basic level of coding knowledge and creating subscriptions requires an experienced developer. I would recommend reaching out to one of our third party developers that can do it all for you. Here is a handy link for you to explore:
https://support.stripe.com/questions/using-stripe-without-programming
--Paying your Sales Reps
For this, you will also need a developer.
-Standard Connect
Built into your typical Sales Rep on-boarding flow, include the OAuth Link. This will re-route them to Stripe and be prompted to enter their entity information to be verified and stored on our servers. Once they have completed the application it will re-route them back to your site to finish up on-boarding. On the back-end Stripe will connect their new Standard Account to your platform.
https://stripe.com/docs/connect/standard-accounts
Your developer can program their payments in one of two ways:
Option 1:
Program Metadata into all the proposals to ensure that each one marks a particular sales rep. Then use that Metadata to communicate with webhooks that will listen for any incoming charges from that Rep. Then it will run the total by your commission calculator and initiate a Separate Transfer to that Rep's Stripe Account. This can be done right away, or you can program it to wait for a period of time.
Option 2:
Have your developer build you a self-service module that will allow you to select a Sales Rep and enter in the amount to be sent to them. Whomever is doing this action can use your commissions calculator to determine the total, and then initiate the Transfer. The code should be set up to generate the right account numbers for that Sales Rep and fire the Separate Transfer. This method would entail more employee hours and wouldn't be automatic.
I'm still waiting to see if we can work out a way to pay your Sales Reps while still using "Better Proposals" but here is my recommendation with the plan of abandoning "Better Proposals" programming and building your functionality with a Developer.
--Accepting Payments from Customers
Since you would like to create a proposal with a way to pay inside, the way I see it you have two options:
Option 1:
Your development team will need to build a user interface for your Sales reps to be able to create this proposal, and assign the subscription plans that are appropriate for this customer. Through your programming your developers can link these plans to the back end subscriptions to ensure that the charge API (through the Gateway) will automatically assign the right plan when the card is charged.
https://stripe.com/docs/subscriptions/quickstart
The proposal should also be built with one of our Gateways** (to collect the customer's payment information in a PCI compliant way) and populate the appropriate subscription API necessary for what the proposal deems.
This will be the most efficient and automatically generated option. Higher in development time/costs, but less hassle to complete by Sales Reps.
Option 2:
Your proposals can have the breakdown of what they are paying for and when, and your developer can include one of our Gateways** but in this case you wouldn't charge anything right away. Your developer would merely integrate the Gateway to collect and store the customer's payment information as an Object ID (and active "Customer" with saved payment information).
https://stripe.com/docs/saving-cards
The the Sales Rep would then log into your Stripe Dashboard (you can give them their own credentials with limited access and control) and access that "Customer" (once their payment Object ID is saved). They can then tweak their subscription to add payment plan amounts and timing.
This method would be less in development costs, but more overall work for the Sales Reps.
--Needing A Developer
Integrating our API requires at least a basic level of coding knowledge and creating subscriptions requires an experienced developer. I would recommend reaching out to one of our third party developers that can do it all for you. Here is a handy link for you to explore:
https://support.stripe.com/questions/using-stripe-without-programming
--Paying your Sales Reps
For this, you will also need a developer.
-Standard Connect
Built into your typical Sales Rep on-boarding flow, include the OAuth Link. This will re-route them to Stripe and be prompted to enter their entity information to be verified and stored on our servers. Once they have completed the application it will re-route them back to your site to finish up on-boarding. On the back-end Stripe will connect their new Standard Account to your platform.
https://stripe.com/docs/connect/standard-accounts
Your developer can program their payments in one of two ways:
Option 1:
Program Metadata into all the proposals to ensure that each one marks a particular sales rep. Then use that Metadata to communicate with webhooks that will listen for any incoming charges from that Rep. Then it will run the total by your commission calculator and initiate a Separate Transfer to that Rep's Stripe Account. This can be done right away, or you can program it to wait for a period of time.
Option 2:
Have your developer build you a self-service module that will allow you to select a Sales Rep and enter in the amount to be sent to them. Whomever is doing this action can use your commissions calculator to determine the total, and then initiate the Transfer. The code should be set up to generate the right account numbers for that Sales Rep and fire the Separate Transfer. This method would entail more employee hours and wouldn't be automatic.
Aly G.
0% (0)Projects Completed
-
Freelancers worked with
-
Projects awarded
0%
Last project
7 May 2024
United Kingdom
New Proposal
Login to your account and send a proposal now to get this project.
Log inClarification Board Ask a Question
-
There are no clarification messages.
We collect cookies to enable the proper functioning and security of our website, and to enhance your experience. By clicking on 'Accept All Cookies', you consent to the use of these cookies. You can change your 'Cookies Settings' at any time. For more information, please read ourCookie Policy
Cookie Settings
Accept All Cookies