{"id":69072,"date":"2026-05-13T10:11:00","date_gmt":"2026-05-13T08:11:00","guid":{"rendered":"https:\/\/www.centralpay.com\/?p=69072"},"modified":"2026-06-03T11:14:41","modified_gmt":"2026-06-03T09:14:41","slug":"integrate-card-payment-into-your-website-api-plugin-or-hosted-solution","status":"publish","type":"post","link":"https:\/\/www.centralpay.com\/en\/blog\/integrate-card-payment-into-your-website-api-plugin-or-hosted-solution\/","title":{"rendered":"Integrate card payment into your website: API, plugin or hosted solution ?"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\"><\/p>\n\n\n\n<h2 class=\"wp-block-heading has-text-align-left\">What integrate card payment really entails<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Before choosing an integration method, it is helpful to understand how a <a href=\"https:\/\/www.centralpay.com\/en\/solutions\/payments\/credit-card\/\">bank card<\/a> transaction works.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">When a customer enters their card number and validates their payment, several actors come into play: the PSP (payment service provider) which orchestrates the transaction, the card network (Visa, Mastercard, CB), the bank that issued the customer&#8217;s card and the acquiring institution which credits the merchant account.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For the developer, integrating card payments means connecting the platform to this payment chain. Several integration methods are possible.<\/p>\n\n\n\n<div style=\"height:30px\" aria-hidden=\"true\" class=\"wp-block-spacer\"><\/div>\n\n\n\n<h2 class=\"wp-block-heading has-text-align-left\">API integration: maximum control, longer implementation time<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\"><a href=\"https:\/\/www.centralpay.com\/en\/solutions\/connect\/api-and-sdk\/\">API integration<\/a> is the most flexible approach. In practice, you build your own payment form and call the PSP endpoints to create payment intents, trigger authorizations, or manage the transaction lifecycle. The business logic is entirely under your control (status management, retries, errors, etc.). Webhooks notify you in real time of each event: payment validated, payment declined, 3DS authorization request, refund.<\/p>\n\n\n\n<div style=\"height:15px\" aria-hidden=\"true\" class=\"wp-block-spacer\"><\/div>\n\n\n\n<h3 class=\"wp-block-heading has-text-align-left\">Benefits<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Customized user experience: the payment module integrates seamlessly into your interface<\/li>\n<\/ul>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Total control over the route and data (excluding sensitive map data, which is managed on the PSP side)<\/li>\n<\/ul>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Ability to manage complex scenarios: subscriptions, recurring payments, installment payments, deferred payments\u2026<\/li>\n<\/ul>\n\n\n\n<ul class=\"wp-block-list\">\n<li>No dependency on a third-party CMS or plugin<\/li>\n<\/ul>\n\n\n\n<div style=\"height:15px\" aria-hidden=\"true\" class=\"wp-block-spacer\"><\/div>\n\n\n\n<h3 class=\"wp-block-heading has-text-align-left\">Disadvantages<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Significant development time (allow several weeks)<\/li>\n<\/ul>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Maintenance to be expected: API updates, library updates\u2026<\/li>\n<\/ul>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Requires good handling of asynchronous states (transactions fail, webhooks arrive out of order)<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">This option is preferable if you have proprietary development, specific business use cases (marketplace, SaaS platform, complex subscriptions) or if the payment experience is a product differentiator.<\/p>\n\n\n\n<div style=\"height:30px\" aria-hidden=\"true\" class=\"wp-block-spacer\"><\/div>\n\n\n\n<h2 class=\"wp-block-heading has-text-align-left\">The CMS plugin: quick implementation, defined scope<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">If your e-commerce store is built on a CMS (<a href=\"https:\/\/www.shopify.com\/fr\" target=\"_blank\" rel=\"noopener\">Shopify<\/a>, Prestashop, Magento\u2026), the plugin is often the most direct way to integrate credit card payment.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The plugin can be installed from the CMS marketplace or directly from the back office. Once your PSP credentials are configured, it handles the payment page, communication with the system, and order status updates.<\/p>\n\n\n\n<div style=\"height:15px\" aria-hidden=\"true\" class=\"wp-block-spacer\"><\/div>\n\n\n\n<h3 class=\"wp-block-heading has-text-align-left\">Benefits<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Deployment in a few hours<\/li>\n<\/ul>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Updates and maintenance are managed by the plugin publisher.<\/li>\n<\/ul>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Native integration with the CMS order tunnel<\/li>\n<\/ul>\n\n\n\n<div style=\"height:15px\" aria-hidden=\"true\" class=\"wp-block-spacer\"><\/div>\n\n\n\n<h3 class=\"wp-block-heading has-text-align-left\">Disadvantages<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Limited customization of the payment page and the user journey<\/li>\n<\/ul>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Dependence on CMS and plugin versions<\/li>\n<\/ul>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Limited functional scope: some complex use cases (recurring payments, subscriptions, etc.) require additional API integration.<\/li>\n<\/ul>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Not all PSPs offer plugins for all CMSs<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">This option is best if you are using a standard CMS, your transaction volume does not justify custom development, and your use case is a classic e-commerce with occasional payments.<\/p>\n\n\n\n<div style=\"height:30px\" aria-hidden=\"true\" class=\"wp-block-spacer\"><\/div>\n\n\n\n<h2 class=\"wp-block-heading has-text-align-left\">The hosted solution: the shortest path<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Integrating card payments through a hosted page is the simplest solution. The PSP provides a URL to which you redirect your customer at the time of payment. This payment page, hosted and maintained by the PSP, handles the payment processing, 3DS verification, and returns the customer to your website once the transaction is complete.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">From a technical standpoint, integration often boils down to a request to create a payment session, a redirection, and the management of a callback or a confirmation webhook.<\/p>\n\n\n\n<div style=\"height:15px\" aria-hidden=\"true\" class=\"wp-block-spacer\"><\/div>\n\n\n\n<h3 class=\"wp-block-heading has-text-align-left\">Benefits<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Minimal integration: a few API calls are all it takes.<\/li>\n<\/ul>\n\n\n\n<ul class=\"wp-block-list\">\n<li>PCI DSS compliance simplified to the maximum: banking data never passes through your server<\/li>\n<\/ul>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Payment security is entirely managed on the PSP side.<\/li>\n<\/ul>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Compatible with all technical environments.<\/li>\n<\/ul>\n\n\n\n<div style=\"height:15px\" aria-hidden=\"true\" class=\"wp-block-spacer\"><\/div>\n\n\n\n<h3 class=\"wp-block-heading has-text-align-left\">Disadvantages<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Disruption in user experience: redirection to an external page can impact conversion rates.<\/li>\n<\/ul>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Limited customization: you can often integrate your logo and a few colors, but control remains restricted.<\/li>\n<\/ul>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Less suitable for complex use cases.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">This option is preferable if you have few development resources available and are looking to collect payments quickly (payment link by email, remote invoicing, VAD).<\/p>\n\n\n\n<div style=\"height:30px\" aria-hidden=\"true\" class=\"wp-block-spacer\"><\/div>\n\n\n\n<h2 class=\"wp-block-heading\">The arbitration criteria in practice<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Beyond the characteristics of each approach, several factors should guide your choice.&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The nature of your transactions : A traditional e-commerce site with one-off credit card payments doesn&#8217;t have the same needs as a SaaS platform managing recurring subscriptions or a marketplace distributing payments among multiple merchants. The more complex the use case, the more essential an API becomes.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Your PCI DSS compliance level : Directly handling card data exposes you to significant compliance obligations. Some integration options require dedicated, in-house security expertise.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Your ability to maintain integration: A well-executed API integration from the outset can become a lasting technical asset. Anticipate maintenance needs: PSP updates, management of new authentication methods (soon PSD3), and the addition of new payment methods.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Time-to-market : If the goal is to integrate card payments quickly, a simplified integration should be prioritized.<\/p>\n\n\n\n<div style=\"height:30px\" aria-hidden=\"true\" class=\"wp-block-spacer\"><\/div>\n\n\n\n<h2 class=\"wp-block-heading has-text-align-left\">What changes when you work with an approved EME ?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">An authorized payment institution controls the entire chain: collection and management of funds. For the developer, this translates into fewer intermediaries in the technical chain, better traceability of transactions, and the ability to manage advanced use cases (escrow, payouts to third parties, merchant accounts) from a single API.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">This is particularly relevant if your platform is intended to manage financial flows on behalf of third parties, such as marketplaces, merchant networks, etc.<\/p>\n\n\n\n<div style=\"height:30px\" aria-hidden=\"true\" class=\"wp-block-spacer\"><\/div>\n\n\n\n<div class=\"wp-block-buttons is-content-justification-center is-layout-flex wp-container-core-buttons-is-layout-fe48e5de wp-block-buttons-is-layout-flex\">\n<div class=\"wp-block-button is-style-outline is-style-outline--1\"><a class=\"wp-block-button__link wp-element-button\" href=\"https:\/\/www.centralpay.com\/en\/solutions\/connect\/erp-connectors\/\">Discover how to integrate CentralPay payment services \u2192<\/a><\/div>\n<\/div>\n\n\n\n<div style=\"height:30px\" aria-hidden=\"true\" class=\"wp-block-spacer\"><\/div>\n\n\n\n<script type=\"application\/ld+json\">\n{\n  \"@context\": \"https:\/\/schema.org\",\n  \"@type\": \"BlogPosting\",\n  \"name\": \"Integrate card payment into your website: API, plugin or hosted solution ?\",\n  \"headline\": \"Integrate card payment : which solution to choose ? \",\n  \"datePublished\": \"May 13, 2026\",\n  \"dateModified\": \"May 13, 2026\",\n  \"description\": \"API, CMS plugin or hosted solution : how to choose the right method to integrate card payment ?\",\n  \"image\": {\n  \"@type\": \"ImageObject\",\n  \"height\": \"600\",\n  \"width\": \"1000\",\n  \"url\": \"https:\/\/www.centralpay.com\/wp-content\/uploads\/2026\/05\/integrer-le-paiement-par-carte.jpg\"\n  },\n  \"author\": {\n  \"@type\": \"Person\",\n  \"name\": \"CentralPay\"\n  },\n  \"publisher\": {\n  \"@type\": \"Organization\",\n  \"name\": \"CentralPay\",\n  \"logo\": {\n  \"@type\": \"imageObject\",\n  \"url\": \"https:\/\/www.centralpay.com\/assets\/images\/logo.png\"\n  }\n  },\n  \"mainEntityOfPage\": true,\n  \"url\": \"https:\/\/www.centralpay.com\/en\/blog\/integrate-card-payment-into-your-website-api-plugin-or-hosted-solution\/\"\n}\n<\/script>\n\n\n\n<p class=\"wp-block-paragraph\"><\/p>\n","protected":false},"excerpt":{"rendered":"<p>You need to integrate credit card payments into your website or platform. You&#8217;ve identified a payment service provider. The real question remains: which integration method best suits your tech stack, your constraints, and your ambitions?<\/p>\n<p>Three main approaches exist: API integration, CMS plugins, and hosted payment solutions. They are not suited to the same contexts, do not require the same resources, and do not offer the same level of control.<\/p>\n<p>In this article, discover how to choose the right one.<\/p>\n","protected":false},"author":1,"featured_media":69027,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[171],"tags":[],"class_list":["post-69072","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-use-cases"],"acf":[],"_links":{"self":[{"href":"https:\/\/www.centralpay.com\/en\/wp-json\/wp\/v2\/posts\/69072","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.centralpay.com\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.centralpay.com\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.centralpay.com\/en\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.centralpay.com\/en\/wp-json\/wp\/v2\/comments?post=69072"}],"version-history":[{"count":0,"href":"https:\/\/www.centralpay.com\/en\/wp-json\/wp\/v2\/posts\/69072\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.centralpay.com\/en\/wp-json\/wp\/v2\/media\/69027"}],"wp:attachment":[{"href":"https:\/\/www.centralpay.com\/en\/wp-json\/wp\/v2\/media?parent=69072"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.centralpay.com\/en\/wp-json\/wp\/v2\/categories?post=69072"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.centralpay.com\/en\/wp-json\/wp\/v2\/tags?post=69072"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}