Documentation
  • Documentation
  • Requirements
    • API Settings
  • Web SDKs and APIs
    • Components
    • Form (redirect)
      • Introduction
        • Demo Client (Test Client)
        • 3D Secure
      • Variables - names, lengths and formats
        • How to calculate digest
        • Supported Card Issuers
        • Form Rules
        • Installments
        • Tokenize Brands
        • Custom Params
        • Custom Attributes
        • Supported Payment Methods
        • Transaction Types
      • Notifications
    • LightBox
  • eCommerce Plugins
    • WooCommerce
    • Magento
    • Prestashop
  • Mobile SDKs
  • API Documentation
    • API v1
      • Direct API
      • Transaction management
    • API v2
      • Requirements - API v2
      • Payment API
      • Pay By Link API
      • Payment Method API
      • Token API
      • Customers API
      • Card on File Payment
      • Subscriptions
        • Create Subscription
        • Update Subscription
        • Create/Update/Get Response
      • Customer Subscription
        • Create Customer Subscription
        • Update Customer Subscription
        • Create/Update/Get Response
      • Recurring payments
    • Notifications
    • List of response codes
  • WebRisk
  • 🟣Knowledge Center
    • Payments
    • WebPay Account
Powered by GitBook
On this page
  1. Web SDKs and APIs
  2. Form (redirect)

Introduction

PreviousForm (redirect)NextDemo Client (Test Client)

Last updated 1 year ago

WebPay Form is a simple web service; merchant should collect data consisted of buyer's profile and order info at his site and submit that data to using HTTP POST method.

IMPORTANT Parametrize https://ipgtest.monri.com URL, in production mode the subdomain will be different.

After a valid request is made to WebPay service, a payment form is presented to the buyer.

You can find a demo on this link

Buyer now fills in the card details and submits the form.

Service issues a request for authorization to acquirer bank and redisplays appropriate message if authorization is declined.

If authorization is approved, a redirect is made back to a merchant site.

NOTICE Buyer stays at our side if transaction is declined, form is redisplayed with appropriate message. There is no means to communicate the failure of transaction to merchant at this point.

Optionally, email messages are sent to merchant and/or buyer to notify both sides of successful purchase. This setting is available under merchant account together with custom email templates for outgoing email message.

https://ipgtest.monri.com/v2/form
Demo Redirect