For online payment, the merchant decides which approaches fit the business requirements.

Integration approach	Hosted payment page	Seamless integration	In-page checkout	Mobile XDK	Direct server API + CSE	Recurring API
Browser dependency	Yes, popup and redirection	Yes, popup and redirection	Yes, iframe, popup and redirection	Smartphone built-in browser	Depends	No
UI/UX	Moderate	Better	Better	Best for mobile	Handled by merchant	Handled by merchant
Time to market (man-day)	1–7	2–14	2–14	2–14	5–60	10–90
Suitable for	Fast and easy deployment	Better UX	Better UX	In-app purchase	Better UI & UX	Subscription or billing
Mobile readiness	RWD	RWD	RWD	Native / hybrid	Backend only	Backend only
PCI-DSS compliant	PG	PG	PG	PG	PG / Merchant if handling PAN	PG / Merchant if handling PAN
Availability on github	20/22 of the cart modules	6/22 of the cart modules	Yes	12 dev-tools supported	nil	nil
Available endpoints	all 3 endpoints	all 3 endpoints	all 3 endpoints	notification & callback URL	all 3 endpoints	notification & callback URL
Fraud screening	By PG	By PG	By PG	By PG	By merchant	By merchant

For response handling, setup these endpoints (webhook) to capture the payment response.

Response endpoint	Return URL	Notification URL	Callback URL
Browser dependency	Yes	No	No
Payment type response	Realtime payment	Realtime payment	Cash payment / defer update
Reliability	Low	High	High
Security	Low if payment verification is not enabled	High	High
IPN implementation	Frontend: easier to implement using JS snippet with treq=0 Backend: POST back all values + treq=1 to returnipn.php, more reliable	Backend: POST back all the values + treq=1 to returnipn.php	Backend: echo "CBTOKEN: MPSTATOK"