Yapi Kredi describes Virtual POS applications under POSNET and discusses foreign-currency transactions in its merchant FAQ. Base the MagicPay scope review on the existing store configuration and keep order pricing, transaction results and the collection account aligned.
Match POSNET sale currency to the account
The official answer discusses USD and EUR transactions, including Virtual POS. Confirm which currency is enabled for the merchant before testing. Record the amount, currency and bank reference together so that finance does not confuse identical amounts denominated in different currencies.
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 POSNET 3DS model against current technical scope. | Not yet confirmed |
| Installments | Confirm the scope with us Clarify Virtual POS installment options for the merchant. | Not yet confirmed |
| Refund | Confirm the scope with us Confirm refunds separately from general POS cancellation information. | Not yet confirmed |
| Partial refund | Confirm the scope with us Partial refunds require Virtual POS-specific technical scope. | Not yet confirmed |
| Card storage | Confirm the scope with us Card storage is not documented in the reviewed source. | Not yet confirmed |
| Currency | Subject to merchant terms USD and EUR are described for Virtual POS; use depends on account permission. Official source | 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 Yapı Kredi 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 Yapı Kredi records. Keep order references, completed payments, pending authorizations where applicable and confirmed refund results distinct.
Frequently asked questions
What should a foreign-currency sale record include?
Link the order amount, currency and bank transaction reference in one record. Finance can compare these with the collection account and its enabled currency.
Can the review start with an existing Yapı Kredi 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.