Help Center
Current article

Recommendations for designing a billing interface

A token is an encrypted representation of a customer’s bank card stored in the payment system. It allows you to charge the card without asking the customer to re-enter card details.

If you use tokens API for subscriptions or recurring payments, your billing interface should be simple, clear, and transparent.

Automatic retry attempts

If a payment fails (for example, due to insufficient funds), set up automatic retry attempts.

It is recommended to make up to 5-7 attempts, gradually increasing the interval between them — for example, after 1 day, then 2 days, then 3 days, and so on.

Always notify the customer about the failed charge and give them time to top up their account or update their card before the next attempt.

Manual retry option

Add a “Retry payment” button so the customer can manually attempt the charge again after resolving the issue.

If there are failed payments, this section should remain accessible and not be blocked.

Allow multiple cards

Let customers add a second card as a backup payment method.

First attempt to charge the primary card. If it fails, try the backup card. This reduces the risk of service interruption.

Display refunds in transaction history

If a refund is issued, it should be clearly visible in the transaction history.

Show the refund amount, date, and the related transaction. This improves transparency and reduces confusion.

Easy cancellation

The unsubscribe button should be visible and easy to access.

Do not automatically delete the saved card after cancellation unless the customer explicitly requests it. This allows them to resume the subscription without re-entering card details.

Clear pricing information

The interface should clearly show:

– subscription price
– taxes
– fees
– total amount charged

Customers should understand exactly what they are paying for.

Notifications

Inform customers about important events such as:

– failed charges
– successful renewals
– refunds

Notifications can be sent by email or any other available channel.

The main goal is to make billing predictable and transparent. The fewer surprises customers face, the fewer cancellations, complaints, and chargebacks you will have.

Best practices for designing a user-friendly billing interface to charge payments using tokens: enhance usability, automate error handling, ensure transparency, and improve customer satisfaction.
Related articles
Article categories
API
Updates
Track major updates on the Allpay Telegram channel (ad-free).
Subscribe

FAQ

Can Allpay be integrated into a website created with AI?

Yes. Just as you used AI to build your website, you can ask AI to integrate payments via Allpay. See the recommendations and example prompts.

Do you have webhooks?

Yes, Allpay can send a webhook for a successful payment. Learn more.

Does your API support hosted fields?

Yes. Card input fields can be embedded into your website or app, fully adapting their design. Learn more about Hosted Fields.