Displaying payment details#
Your customer pays by typing the details you show into their bank app. A clear payment screen is the biggest factor in whether they pay the right amount, to the right account, before it expires. This page covers what to show, how to lay it out and how to confirm the payment.
Transfer exactly
₦25,000.00
- Bank
- Partner Bank
- Account number
- 991 234 5678
- Account name
- ACME STORES / YUSR
Pay before 14:30, in 29:41
Waiting for your transfer
What to show#
Everything comes from the payment object of the transaction:
| Element | Field | Guidance |
|---|---|---|
| Amount | payment.amount | Show it first and largest, formatted in naira (₦25,000.00). Say exactly. |
| Bank | payment.bank_name | Show the value from the response. It can vary between transactions, so never hard-code it. |
| Account number | payment.account_number | Group as 3-3-4 for reading (991 234 5678), but copy the plain 10 digits. |
| Account name | payment.account_name | Tell the customer they will see this name in their bank app. It confirms they're paying you. |
| Expiry | payment.expires_at | Show a countdown and the clock time ("Pay before 14:30"). |
| Status | status | "Waiting for your transfer", then "Payment received" when confirmed. |
Prepare the checkout on your server#
Create the transaction and a client token on your server, then pass only what the page needs. Never send your secret key, and don't trust prices sent by the browser: compute the amount on the server.
Use the ready-made widget#
The fastest route is renderPaymentWidget from @yusr/js. It follows every guideline on this page:
copy buttons with screen-reader announcements, a countdown, a live status region and a success state.
Match it to your brand with CSS variables on .yusr-widget, such as --yusr-accent,
--yusr-radius and --yusr-font. The root element also carries data-status and data-tone
attributes for your own styles.
Build your own#
If you design your own screen, this React component shows the essentials: formatted amount, grouped account number with copy buttons, a countdown and a live status driven by realtime events.
Layout and copy guidelines#
Amount#
- Show the amount in naira with two decimals, and say "exactly": "Transfer exactly ₦25,000.00".
- Warn that bank charges must not be deducted from the amount. If the customer's bank adds a transfer fee, it is charged on top; the amount that arrives must match.
- Offer a copy button that copies the number without the currency symbol or separators (
25000), which bank apps accept.
Account number#
- Group the digits as
991 234 5678so they're easy to read aloud and type, but copy the unbroken9912345678. - Use a monospaced or tabular-numbers font so digits don't shift.
- Each account number belongs to one transaction. Never reuse it for another order, print it on invoices for future use, or save it as a customer's "permanent" account.
Bank and account name#
- Show the bank exactly as returned: the customer has to pick it from a list in their app.
- Explain the account name: "You'll see ACME STORES / YUSR when you enter the account number." That confirmation is what reassures customers they're paying the right business.
Expiry#
- Show a countdown from
payment.expires_at, and the clock time for customers who switch apps. - Calculate the countdown from the server's
expires_at, not from when the page loaded. Device clocks can be wrong; if precision matters, send your server's current time with the page and correct for the difference. - When the countdown reaches zero, stop showing the account details and offer to start again with a new transaction (new reference).
- Choose an
expires_inthat fits how people pay: 30 minutes for an online checkout, up to 72 hours for an invoice.
One transaction per attempt#
Create a transaction when the customer reaches the payment step, and create a new one if they come back after it expires or change their basket. Reusing an old account number leads to late payments that need manual handling.
Confirm the payment#
Show a waiting state ("Waiting for your transfer…") and switch to a clear success state as soon as the payment is confirmed. Customers often stay on the page while they pay from their phone.
- In the browser, use realtime with a client token. The widget and
subscribeToTransactiondo this for you. - Fulfil the order on your server from the verified webhook, never from the browser event.
- If the customer reloads the page, render the latest state from your server (updated by webhooks).
Handle the edge cases#
| Status | What to tell the customer |
|---|---|
underpaid | "We received ₦12,500.00 of ₦25,000.00. Send the remaining ₦12,500.00 to the same account before it expires." |
overpaid | "Payment received. You sent more than the amount due; we'll be in touch about the difference." |
expired | "This account has expired. Don't send money to it. Start a new payment to get a fresh account." |
late_payment | "Your transfer arrived after the account expired. We've received it and our team will follow up." |
cancelled | "This payment was cancelled. Don't send money to this account." |
What happens to under-, over- and late payments is set in Settings → Payment behaviour: accept them, or refund them to the payer's account. Make sure your customer messages match your settings.
Accessibility#
- Use real
<button>elements for copy actions, with labels such as "Copy account number", and announce "Copied" through anaria-liveregion. - Put the payment status in a
role="status"region so screen readers announce "Payment received" without the customer moving focus. - Don't rely on colour alone: pair status colours with text and icons.
- Keep text selectable, so customers can copy details even if the clipboard API is blocked.
- Make sure the layout works at 360 px wide, with copy buttons at least 44 px tall for touch.
- Don't update the countdown in a live region every second; announce only important changes, such as one minute remaining.