Penny Drop is one of seven APIs in the selected Banking Services family. Product teams can place it before a payout or other account-dependent step when their workflow calls for a bank-account check.
A simple product flow
A Penny Drop integration usually follows three product stages:
- Collect the supported account details required by your configured API contract.
- Submit the request from your backend.
- Use the returned status and available fields in your beneficiary or account-review rules.
The exact inputs and response fields depend on the service contract, so use the endpoint documentation supplied during onboarding rather than assuming a universal payload.
Penny Drop or another Banking API?
Choose the endpoint that matches the input already present in your journey.
- Penny Drop supports a bank-account-check workflow.
- Penny Less provides the selected alternative for a penny-less workflow.
- Mobile to Account starts from a supported mobile-number input.
- Mobile to VPA and VPA to Name support selected VPA-oriented flows.
Cheque OCR and Face Match are also part of the focused Banking family, but they solve different product steps.
Integration considerations
- Keep API credentials on the server.
- Validate inputs before sending a request.
- Handle incomplete, unsuccessful and technical responses explicitly.
- Avoid logging bank or identity details unnecessarily.
- Keep your payout decision rules separate from the API client.
Explore the Penny Drop API, or contact our team to discuss the Banking APIs in your flow.