-
Notifications
You must be signed in to change notification settings - Fork 41
feature(bill payments): plan mdm integration guide #278
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
Checklist to merge a PR 🚀To merge this pull request, please take time to complete the checklist. What action did you perform?Review the corresponding checklist items for the action you performed and mark them done. Edit an existing content (MDX) pageChecklist
Edit an existing API reference pageChecklist
Add a new content (MDX) pageChecklist
Add a new API reference pageChecklist
|
### Key Use Cases | ||
- **Mobile Prepaid Recharges** - Choose data/talk time plans | ||
- **DTH Services** - Select channel packages and validity periods | ||
- **Mutual Fund Houses** - Investment plan subscriptions |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We don't have mutual funds as a category right now.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Lets just keep mobile prepaid recharges and DTH right now
### Benefits | ||
- **Seamless Integration** - Replicate existing user flows within BBPS | ||
- **Flexible Plan Management** - Support both static and dynamic plan offerings | ||
- **Real-time Updates** - Webhook notifications for plan changes | ||
- **Standardized API** - Consistent integration patterns across biller types |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Lets compress these 4 points into smaller points that are more intuitive and relevant for API clients
| Step | Actor | Action | API Endpoint | | ||
|------|--------|--------|--------------| | ||
| 1 | Customer | Initiates service subscription | - | | ||
| 2 | App/Platform | Retrieve available plans | `GET /api/v2/bbps/billers/plans` | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can change App/Platform to Your App
| 5 | App/Platform | Validate customer details with plan ID | `POST /api/v2/bbps/bills/fetch/request` | | ||
| 6 | Setu API | Forward validation to biller | - | | ||
| 7 | Biller | Validate account and plan compatibility | - | | ||
| 8 | App/Platform | Check validation status | `POST /api/v2/bbps/bills/fetch/response` | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Same change for Your App. Also, alternate way of getting status is via webhook
**Start Here:** What type of biller are you integrating? | ||
|
||
``` | ||
Is planRequirement = "MANDATORY"? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
planRequirement is a field obtained from the list billers api
No description provided.