Fibabanka's commercial-customer page describes account opening through FibabankaBiz Mobile and video-assisted onboarding. These steps are separate from the merchant payment connection. Prepare the account owner, online sales channel and store configuration for a MagicPay review.
Separate business-account onboarding from store setup
The account owner should identify the merchant agreement and product while the developer checks the current technical documents against the store configuration. Finance can then match a sample order, amount and payment reference to the intended account. An account-opening process does not establish Virtual POS feature support.
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 the merchant 3DS model in technical documentation. | Not yet confirmed |
| Installments | Confirm the scope with us Establish Virtual POS installment permissions separately. | Not yet confirmed |
| Refund | Confirm the scope with us An account-opening refund does not prove merchant refund support. | Not yet confirmed |
| Partial refund | Confirm the scope with us Confirm the transaction scope for partial refunds. | Not yet confirmed |
| Card storage | Confirm the scope with us Verify the card-storage service and reference model. | Not yet confirmed |
| Currency | Subject to merchant terms The currency depends on the approved sales-account configuration. | Not yet confirmed |
| Preauthorization | Confirm the scope with us Clarify preauthorization for the relevant Virtual POS product. | Not yet confirmed |
Plan your MagicPay connection in three steps
Review the Fibabanka 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 Fibabanka records. Keep order references, completed payments, pending authorizations where applicable and confirmed refund results distinct.
Frequently asked questions
Does commercial-account onboarding establish the payment integration scope?
No. Account opening and merchant integration are different steps. Match the existing merchant product and store details to current technical documentation before defining acceptance tests.
Can the review start with an existing Fibabanka 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.