Tami presents hosted checkout, payment links and Masterpass for different shopping journeys. Review how the existing store sends customers to payment and brings them back to the order, with scope confirmed for the current merchant account.
Review Masterpass within hosted checkout
Tami describes Masterpass together with its hosted payment page. A stored-card review must therefore include where payment happens, not just card storage as an isolated feature. Follow the transition from the store cart to checkout and back to the order with traceable references.
Payment capabilities and integration scope
This table distinguishes published provider capabilities from merchant-specific conditions. A feature offered by a provider is not automatically enabled on every MagicPay connection.
| Capability | Scope and conditions | In MagicPay |
|---|---|---|
| 3D Secure | In provider documentation The Tami Virtual POS page mentions 3DS infrastructure. Official source | Not yet confirmed |
| Installments | Subject to merchant terms Installments for participating card programs depend on account scope. Official source | Not yet confirmed |
| Refund | Confirm the scope with us Clarify refund-service permission and transaction conditions. | Not yet confirmed |
| Partial refund | Confirm the scope with us Confirm partial refunds in technical documentation. | Not yet confirmed |
| Card storage | Subject to merchant terms Masterpass is offered within Tami's hosted payment-page scope. Official source | Not yet confirmed |
| Currency | Confirm the scope with us Verify currencies against the merchant account's product scope. | Not yet confirmed |
| Preauthorization | Confirm the scope with us Confirm preauthorization and capture separately. | Not yet confirmed |
Plan your MagicPay connection in three steps
Review the Tami account
Identify the existing merchant agreement, sales channel, store configuration and enabled products. Confirm the required payment scenarios and the separate MagicPay connection scope before activation.
Test the approved configuration
Authorized technical staff should configure credentials through a secure server-side channel. Compare successful, rejected and interrupted payments, and test refund or stored-card scenarios only where their scope has been confirmed.
Reconcile orders and payment results
After acceptance, compare the enabled transaction flows with Tami records. Keep order references, completed payments, pending authorizations where applicable and confirmed refund results distinct.
Frequently asked questions
Can Masterpass be reviewed independently of the checkout model?
The cited Tami material presents it within hosted checkout. Review the page where the customer pays, the store transition and the final order result together.
Can the review start with an existing Tami account?
Yes. Start with the current merchant product and agreement. Account permissions, technical access and the independently confirmed MagicPay scope must be reviewed before deciding which flows can be activated.
Does provider documentation confirm that a feature is ready in MagicPay?
No. The provider notes describe its published scope and merchant conditions. The separate In MagicPay column remains Not yet confirmed until the technical connection scope is independently verified.