Garanti BBVA's developer portal documents sales, refunds, capture and queries as separate transaction groups. Review the existing merchant agreement together with order payment and post-sale tracking, especially when a basket contains multiple items.
Keep full and partial refund records distinct
The refund documentation distinguishes returning the entire payment from returning part of it. Prepare a multi-item order and decide how finance will track the returned item and remaining collected amount. Keep the bank transaction reference with the order and distinguish a refund request from its completed result.
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 developer portal includes a 3DS sale flow. Official source | Not yet confirmed |
| Installments | Subject to merchant terms Installment sales are documented; enabled choices depend on store permissions. Official source | Not yet confirmed |
| Refund | In provider documentation Provider documentation describes refunding the full amount to the card. Official source | Not yet confirmed |
| Partial refund | In provider documentation Partial refunds are defined separately. Official source | Not yet confirmed |
| Card storage | In provider documentation The bank offers card storage as a separate e-commerce service. Official source | Not yet confirmed |
| Currency | Subject to merchant terms Currencies depend on the store's enabled transaction permissions. | Not yet confirmed |
| Preauthorization | In provider documentation Provider documentation defines preauthorization and subsequent capture. Official source | Not yet confirmed |
Plan your MagicPay connection in three steps
Review the Garanti BBVA 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 Garanti BBVA records. Keep order references, completed payments, pending authorizations where applicable and confirmed refund results distinct.
Frequently asked questions
What should a partial-refund example retain?
Keep the original order, bank transaction reference, returned item, refunded amount and remaining collected amount together. Track the completed refund result separately from the request.
Can the review start with an existing Garanti BBVA 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.