Payments and delivery for a shop in Moldova

Define online payments, bank transfers or cash on delivery according to products and audience. Clarify countries and currency. Confirm merchant eligibility, contracts and current tariffs directly with the provider before implementation.

maib and Paynet publish merchant solutions. Review current offerings and documentation, then confirm connection to your shop platform. Availability of a payment service does not imply compatibility with every platform, plan or business model.

Sources

• maib — e-commerce
• Paynet — merchant solutions

Creating an order does not mean it is paid. Define pending, confirmed, rejected and refunded states. Follow the provider’s confirmation flow rather than relying only on a customer returning to a success page. Repeated notifications should not create another order.

• A shared order and payment identifier
• Rules for delayed confirmation
• Retrying a failed payment
• Tracked cancellations and refunds
• Alerts for unresolved incidents

Specify areas, tariffs, communicated lead times and weight or size limits. Decide between manual shipments and integration. Poșta Moldovei and Nova Post API documentation are starting points; confirm actual access and services with providers.

Sources

• Poșta Moldovei — API
• Nova Post — API

Define when inventory is reserved, availability decreases and cancellations release reservations. An unpaid order may require different rules from a confirmed one. Staff need to see blocked orders and exceptions.

Separate implementation from payment fees, courier tariffs and maintenance. Prepare test accounts and agreed provider scenarios. Midavco confirms integrations after reviewing platform, documentation and access; naming a provider does not imply partnership.