maib e-commerce API
RORU
  • Terminology
  • Integration steps and requirements
    • Integration steps
    • Integration requirements
  • maib e-commerce API
  • Payments types
  • Access Token generation
  • Direct payment
  • Two-step payment
    • Payment authorization
    • Payment capture
  • Payment refund
  • Payment information
  • Recurring payments
    • Register card in the maib ecomm system
    • Execute recurring payment
  • One-click payments
    • Register card in the maib ecomm system
    • Execute one-click payment
  • Deleting the card from maib ecomm
  • Notifications on Callback Url
  • Transaction and 3D-Secure status
  • Errors
    • API errors
    • HTTP status codes
  • Plugins and Solutions
    • Plugins
    • SDK
    • Tilda
    • Gomag
    • Cartum
    • ECOM
Powered by GitBook
On this page
  • API Endpoints
  • Interaction via API
  • Postman Collection

maib e-commerce API

Interaction with maib ecomm occurs through HTTPS (POST / GET / DELETE) requests to API endpoints with data in JSON format.

The responses received on the website/app from maib ecomm will be HTTPS POST requests with data in JSON format.

All endpoints are structured according to the following pattern: {base-url}/{api-version}/{point}

Base URL: https://api.maibmerchants.md

Current API version: v1

API Endpoints

Endpoint
Description

https://api.maibmerchants.md/v1/generate-token

https://api.maibmerchants.md/v1/pay

https://api.maibmerchants.md/v1/hold

https://api.maibmerchants.md/v1/complete

https://api.maibmerchants.md/v1/refund

https://api.maibmerchants.md/v1/pay-info

https://api.maibmerchants.md/v1/savecard-recurring

https://api.maibmerchants.md/v1/execute-recurring

https://api.maibmerchants.md/v1/savecard-oneclick

https://api.maibmerchants.md/v1/execute-oneclick

https://api.maibmerchants.md/v1/delete-card

Interaction via API

E.g for Direct Payment:

  1. Customer chooses product or service in Merchant online shop (website/app) and adds it to his cart.

  2. The Customer presses the «Place order» button, and the Merchant sends an HTTPS POST request (with transaction data) to the API endpoint.

  3. maib ecomm returns an intermediate response containing the link (payUrl).

  4. The Customer is redirected to the payUrl link and access the maib ecomm checkout page.

  5. The Customer enters the card data (or pay via Apple Pay/Google Pay).

  6. The maib ecomm processes the transaction.

  7. The Customer is redirected back to the Merchant online shop (website/app), on okUrl or failUrl (depending on the status of the transaction).

  8. The Merchant online shop receives (on callbackUrl via HTTPS POST request) a final response containing the status and basic transaction data.

Postman Collection

PreviousIntegration requirementsNextPayments types

Last updated 1 year ago

(two-step payments)

(two-step payments)

(recurring payments)

(recurring payments)

(one-click payments)

(one-click payments)

(recurring and one-click payments)

Access Token generation
Direct payment
Payment authorization
Payment capture
Payment refund
Payment information
Register card
Execute recurring payment
Register card
Execute one-click payment
Deleting the card
3KB
API_maib_e-commerce.postman_collection.zip
archive