Direct payment is a distinct buying path
The current Direct Pay settings support UPI and bank details for stores using that workflow. The storefront explains that the customer places an order, then pays from their own app. It does not tell the buyer that tapping an order button has collected money.
Keep the recipient data accurate
The merchant form saves a complete replacement of the submitted methods. That matters when updating one field: review the whole intended configuration so a partial edit does not unintentionally remove a method. Existing sensitive values are represented through masked on-file information rather than a full secret read-back.
Record receipt only after verifying it
The merchant must reconcile the transfer through the actual bank or payment record. An order status or customer screenshot is not independent proof of receipt. The Clear due action in order details records received money; it does not initiate a charge. Keep that distinction clear for anyone operating the account.
Check availability rather than assuming it
The settings can refuse changes when secure storage is unavailable. A connected gateway can also change which payment path customers see. Confirm the current account configuration and checkout before advertising a method. This page does not promise instant settlement, automatic bank reconciliation or recovery of an incorrectly addressed transfer.
UNDERSTANDING THE WORKFLOW
UPI details explain where to pay, not whether payment arrived
Showing a UPI ID or bank details gives a buyer a destination for a direct payment. It does not establish that the transfer succeeded.
What the merchant interface says The inspected payout-details screen explains a flow for stores without a payment gateway: the customer places an order, sees the details and pays from their own app. It explicitly tells the merchant to confirm receipt in their own bank or UPI app before accepting the order.
The same source includes a locked state when secure server storage is unavailable. Do not promise universal availability simply because the fields exist in the code.
Separate the evidence A customer reference or screenshot is a claim to investigate, not a substitute for checking the actual receiving account. Compare the intended order and amount with the funds received through your normal authorised process.
What this does not promise Direct-pay details are not automated bank reconciliation, a payout timetable or a gateway integration. Avoid language suggesting that every displayed payment claim is already verified.
Use the direct-pay feature page for the supported workflow. A release announcement about these controls still requires matching deployed app/backend evidence and an authorised account test.
Bring this checklist to your evaluation
- Verified recipient details
- Complete method replacement reviewed
- Enabled state confirmed
- A genuine receipt-checking routine
Check the workflow that matters to your business
Read the relevant setup and troubleshooting guide, then explore getting started with oBizee. Confirm current account availability and terms before committing.