Week 10 Payment Split Works -> Pickup

By -

 

 Title : Payment Split when a users pickups a food works

Author Sampurna Adhikari

-> When a users checkout with the Pickup option, the total fees is being split between the Food Lister, Platform(Our Fee) and stripe fee.

Logs: 

When a user pays for food the backend creates a Stripe PaymentIntent which is 

transfer_data.destination is the donor stripe account which is connected via profile
.

application_fee_amount  which is platform’s marketplace fee and stripe automatically deducts processing fees from the connected account’s payout.


here the total amount 11.17 is charged to a user paying for the food then we take 2.20 as our fee and the rest is then transfered to the donor stripe account.

Comments

Post a Comment

Popular posts from this blog

Additional week 1- My Contributions to the Community Fridge Locator & Food Listing Design

By -
Image
In Week 5, my teammate Sagar Chaudhary first introduced the concept of Community fridge locator as a part of our brainstorming on new features . This week, I advanced that concept by progressing into the design and technical planning phase, creating specific workflows, comparisons, and visuals that will steer development in the upcoming  development phgase. Community Refrigerator Finder – My Design Project I started by researching mapping APIs to find the best option for FoodNextDoor . I evaluated two   primary services: Google Maps API: extensive global reach (99%) and highly reliable (Google Maps Platform, 2025) . Mapbox: extensively adaptable with offline map capabilities, enabling distinctive fridge pin symbols (Choosing a Map API for Your Next App: Mapbox, Google Maps, or OpenStreetMap ? 2021). Expanding on Sagar’s original concept, I proposed that fridge locations be marked with color-coded pins: I suggested incorporating filters that allow...
Read more

Week 9 Survey

By -
Image
Author : Sampurna Adhikari Title : Survey  In order to obtain important information and public opinion about the project we are working on, a survey was carried out this week. This survey's main objective was to find out how prospective users felt about the system's main concept, features, and general usefulness. We wanted to gather both qualitative and quantitative input from a wide range of people so that we could make well-informed decisions about design and development. Users' expectations, current obstacles, and what features they would most value in an approach similar to ours were all covered in the survey. It also aimed to evaluate the degree of trust, interest, and readiness to embrace the idea after it is put into action. All things considered, the feedback collected through this survey will be extremely important in determining the project's future course. Plan for this Week This week, the focus will be on wrapping up the research phase by compiling finding...
Read more

Additional 3 - Notification & Reminder System Design

By -
Image
  Following on from last work on the Booking & Reservation system, my focus this week was on designing the Notification & Reminder System. Its purpose is to keep users informed about their bookings, reduce no-shows, and strengthen trust within the FoodNextDoor platform. The Need for a Notification System According to our previous feasibility study, making sure that reserved items are picked up on time is one of the difficulties in community food redistribution. Food can spoil or other users might miss out if reminders aren't given. Notifications offer an organized method for: Confirm successful reservations. Inform users of the due dates for pickup. Notify donors if any items are not picked up. This directly advances our project's objectives of efficiency and fairness. My Contribution to the Design This week, I contributed by designing the notification workflow and researching the most suitable delivery technologies: Booking confirmation notification – sent immediately ...
Read more