TEB describes application review, delivery of technical documents, user training and testing as separate Virtual POS stages. Use that sequence to assign responsibilities across the bank, technical team and operations when preparing a MagicPay review.
Connect documentation and training to the acceptance plan
Identify the current document version and the store configuration it applies to. Operations should learn how to find a sale and interpret its result, while developers define technical acceptance outcomes. Completing panel training does not by itself prove that the integration has passed its payment and refund tests.
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 | Confirm the scope with us Confirm 3DS using the technical document supplied by TEB. | Not yet confirmed |
| Installments | Confirm the scope with us Verify installment options against store permissions. | Not yet confirmed |
| Refund | Confirm the scope with us Check panel refunds and integration refunds separately. | Not yet confirmed |
| Partial refund | Confirm the scope with us An explicit transaction definition is required for partial refunds. | Not yet confirmed |
| Card storage | Confirm the scope with us Card storage is not technically documented on the product page. | Not yet confirmed |
| Currency | Subject to merchant terms Currencies depend on the merchant's approved account configuration. | Not yet confirmed |
| Preauthorization | Confirm the scope with us Compare preauthorization requirements with TEB's technical scope. | Not yet confirmed |
Plan your MagicPay connection in three steps
Review the TEB 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 TEB records. Keep order references, completed payments, pending authorizations where applicable and confirmed refund results distinct.
Frequently asked questions
When does TEB supply technical documents?
The official process says that the Virtual POS Center contacts the business and supplies documents after application approval. Confirm the applicable version for the existing merchant account.
Can the review start with an existing TEB 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.