A widget embeds directly into the store page: the buyer pays without leaving your site. A payment page opens at a separate address on the provider side. In both cases card details are entered in the provider's secure form and never pass through your server.
How they differ
| Widget | Payment page | |
|---|---|---|
| Where the buyer pays | On your site | On a separate page |
| Styling | Adapts to your site | Provider styling |
| Integration | Embed a block in your markup | Follow a link |
| Mobile flow | No extra hops | Opens as a new page |
Which to choose
A widget when it matters that the buyer never falls out of the store: a long cart, an expensive order, repeat purchases.
A payment page when there is no site or it is simple: selling from a messenger, invoicing after a call, a one-off service. That is essentially a payment link.
What does not differ
- Cost: neither the widget nor the page carries a separate charge.
- Security: a certified provider handles card data either way.
- Payment methods: cards, SBP and Pay services are available in both.
See the payment widget. If you need full control over the design, look at the payment API.
