Connect the checkout only after the corridor is named

What gets connected

A 2d payment gateway integration is the work of joining a shop’s existing site to a card path that an acquirer has already agreed to board. The shopper still types a card number and an expiry date. Whether the issuing bank then asks for its own check is not decided by the plugin. It is decided by the bank, the card network and the country of the card. A shop in India that takes UPI at home does not get a quieter card form for domestic cards just because a plugin was installed. Calling that form a 2d secure payment gateway is a label on other sites. This page does not treat the payment processing as a promise.

The connection can be an API, a hosted page, or a plugin for a shop system the merchant already runs. The choice is written in the file before a developer spends a day on it. A hosted page keeps card data off the merchant’s server. An API is for a team that will store nothing it is not allowed to store. A plugin is for a site that already has a checkout and only needs the methods switched on.

Documents come before the first live payment. The company, the site, the countries of the shoppers, and the methods they actually use are the start of that file. A missing licence, a missing descriptor, or a business model the acquirer will not board stops the work. The page does not promise that every shop is approved, and it does not sell a bypass of the bank’s step.

Signing means who stores the card data and who can open a payment after it is sent. Monitoring means the merchant can read the status of that same payment later. It is not a public score. Webhooks, if the API is the chosen path, are listed with the event names the dashboard will actually send. A return address on the shop’s site is required so the shopper lands somewhere the merchant controls after the attempt. Failed payments stay visible. They are not hidden to improve a chart.

Currencies are named one by one. A shop that settles in rupees and a shop that settles in dollars are two files. The descriptor the shopper sees on a statement is agreed before the test, because a vague descriptor is a common reason a payment is challenged later. Chargebacks can still happen on card payments. A wallet payment is a different rail and is described as such. None of this is waived because the checkout was connected on a Tuesday.

The file is a list, not a brochure. It starts with the legal name of the company, the trading name if it differs, and the country where the company is registered. It names the website the shopper will actually use, including the page where the card form will sit. A staging address is useful for the test, and it is written next to the live address so the two are not confused later. The person who can answer a question about the company is named, with an email that reaches that person. A shared inbox that nobody reads is a common reason a review stalls.

Shopper countries are written as countries, not as “international”. A merchant who sells to people in India writes India. A merchant who also sells to people in the UAE writes the UAE on the same line only if those shoppers use the same site. Two sites are two files. The methods already offered on the site are listed as they appear at checkout today: cards, a local wallet, a bank transfer, a pay-by-link sent in chat. A method the merchant hopes to add later is marked as a request, not as something already live. The acquirer reads the request. The page on this site does not turn the request into a yes.

Settlement is a separate line from the shopper’s currency. A shopper can pay in one currency while the merchant receives another, and only if the acquirer has said that pair is available for that merchant. The file records the bank account that will receive settlement, the name on that account, and whether the account belongs to the same company that owns the site. A personal account for a registered company, or a company account for a sole trader, is a mismatch the reviewer will ask about. This page does not print the account number and does not ask for it in public.

The statement descriptor is the short text a cardholder sees from the bank. It is agreed before any test payment, and it should be recognisable as the shop. A descriptor that is only a processor’s name produces disputes from people who do not remember the purchase. The file also notes the refund path: who on the merchant’s side can start a refund, whether a refund goes back to the same card, and how the order on the site is marked when that happens. Refunds are not the same as a chargeback. A chargeback is the cardholder’s dispute through the bank. Both can occur. Neither is cancelled by the choice of plugin.

Card data has one home in the file. If the home is a hosted page, the merchant’s server receives an order reference and a status, not the card number. If the home is an API that the merchant’s developers build, the file says which fields that API will accept and which fields it must refuse. A plugin sits in between: the store system shows the fields, and the keys that talk to the acquirer are pasted in the merchant’s own admin. Those keys are created for test first. Live keys are a later line in the same file, issued after the test payment is visible. Test keys and live keys are not interchangeable, and a screenshot of either key does not belong in an email thread with people who do not install the site.

The return address is the page on the merchant’s site where the shopper lands after the attempt. Success and failure can be two addresses or one address that reads the status. The file names both. A return address on a domain the merchant does not control is rejected. Webhooks, when the path is an API, are named as events: payment succeeded, payment failed, refund recorded. The merchant’s developer confirms that the order reference in the event is the same reference stored with the order. If the amounts differ, the site stays in test. The dashboard is the place that comparison is made. A chart that hides failed attempts is not part of the note.

India is called out when the shoppers are in India, because a domestic card and a local method are not the same checkout. UPI, a net-banking step, or a wallet confirmation can sit beside a card form. The card form still collects the number and the expiry. A domestic issuer can still ask for its own check. The file says which of those paths the acquirer will actually enable for this merchant. It does not say that every domestic card will skip a check, and it does not say that a plugin setting can force that skip. A shopper paying from outside India on the same site is a second line, because the corridor is different even when the catalogue is the same.

What the file does not contain is as important as what it does. It does not contain a public fee table. It does not contain an approval rate. It does not contain a promise that funds are never held, and it does not contain a number of days that applies to every merchant. Holds, reserves and payout timing are answered for the merchant after the corridor is known, in the same file, not as a slogan on this page. A product that offers to skip the bank’s step is not a line we add. If another company’s page says that, the sentence stays on their page.

The people who touch the file are few. The merchant names one business contact and one technical contact. The reviewer reads the business model before recommending a path. The acquirer says yes or no. The technical note is written only after the yes, and it is sent to the technical contact. A developer who starts building before that note exists is building against a guess. The guess is not the integration. The integration is the note plus the test payment that matches the order.

A change after the note is a new line, not a quiet edit. If the merchant adds a country, a method, or a second site, the reviewer reads that line before the technical contact installs anything new. A checkout that starts offering a wallet because a theme update added the button is not covered by the old note. The old note stays true for the path it named. The new button waits. The same rule applies when the legal name of the company changes, or when settlement moves to a different account. The dashboard user who could see payments yesterday may not be the right user after that change, and the file says so.

The merchant keeps a copy of what was agreed: the path, the methods, the currency, the descriptor, and the date the test payment matched. That copy is the thing to open when a shopper writes in about a charge they do not recognise, or when a developer joins the team later. This website does not store that copy in public. The contact form starts the review. It does not publish the file. Two merchants in the same city, selling different goods, receive two files. Nothing on this page is a template that both of them can paste into a store and call finished.

Five steps, then a test payment

The 2d payment gateway integration follows the same order a reviewer can check. Nothing in the list is a public fee or a public approval rate.

1. Consultation. The specialist reads the business model, the markets and the methods. A gaming site, a travel site and a shop that only sells physical goods are not the same file.
2. Application. The merchant sends the company papers and the site. The list of papers is named in the reply, not guessed here.
3. Acquirer review. The account is prepared only after the acquiring partner says yes. A no is a no.
4. Connection. The technical note says whether the site gets an API, a hosted page, or a plugin, and which person on the merchant side will install it.
5. Test, then live. A test payment is watched in the dashboard. Live traffic starts after that payment is visible, not when the plugin merely says it is installed.

Consultation is a reading, not a pitch. The specialist looks at what the shop sells, where the shoppers are, and which methods the site already shows. A shop that ships physical goods, a shop that sells a download, and a shop that takes a booking are three different files even when they use the same store system. The reply after this step says which path is worth writing up. It can also say that the model is one the acquirer will not board. That answer is part of the work. It is not a failure of the form.

The application is the papers the reply names. Typical papers are the company registration, the identity of the person who signs, the address of the site, and a short description of the goods. The exact list is in the reply, because a travel merchant and a software merchant are not asked for the same attachments. This page does not invent a universal pack, and it does not publish someone else’s pack as if it were ours. Papers are sent through the contact on this site. They are not pasted into a public chat.

Acquirer review is the step the merchant cannot skip by installing software. The acquiring partner reads the file and either prepares an account or declines it. A decline stops the technical work. There is no second button on this page that overrides a decline. If the partner asks for one more document, that request is forwarded to the business contact. The clock, if there is one, belongs to that review. This page does not print a number of days for it.

Connection starts when the account exists. The technical note names the path: hosted page, API, or plugin. It names the person on the merchant’s side who will install it, and it names the environment: test first. The note includes the fields that path expects and the address where the shopper returns. It does not include a public conversion score, and it does not include a line that says the bank’s check is switched off. The merchant’s developer follows the note. A guide copied from another company’s site is not a substitute for the note.

The test payment is a real attempt in the test environment, for a small amount the acquirer allows, or for the test instrument the acquirer provides. The person watching it checks three things. The order reference on the site matches the reference in the dashboard. The amount matches. The status is the status the shopper was shown, including a deliberate failure if the test plan includes one. Live keys are requested only after those three match. Traffic from real shoppers starts after the live keys are in place and one further payment, still watched, appears in the live view. A plugin screen that says “connected” is not that payment.

What the reviewer reads first

The reviewer reads the file before any path is recommended. The first page of that file is the business: what is sold, to whom, and on which site. A catalogue, a booking calendar, and a download are not described with the same sentence. The reviewer is looking for a model an acquirer can board, not for a slogan about being the fastest checkout on the internet.

Markets come next. India is written as India. Other countries are written by name. A claim that the shop sells “worldwide” is sent back for a list. Methods already on the site are compared with the methods the merchant wants added. A card form for shoppers abroad and a local method for shoppers at home can both be in the file. They are not collapsed into one promise that every payment will look the same.

Risk is read here as a question, not as a badge. The reviewer asks what the shop does if a shopper disputes a card payment, who can issue a refund, and whether the goods are delivered before or after the payment. Gaming, adult, and similar models are named honestly if that is what the site sells. They are reviewed. They are not waved through, and some are refused. A refusal at this step saves the developer from building a checkout that will never be switched on.

Only after that reading does the reviewer say which of the three paths fits: a hosted page, an API, or a plugin. The recommendation is a sentence in the file. It is not a public ranking of providers, and it is not a claim that this company is the only one that can connect a site. The photograph on this block is a folder. The work is the reading.

The reading also checks that the site the shopper will use is the site in the file. A landing page that only collects a name, with the real checkout on another domain, is two sites until the merchant says which one takes the payment. The reviewer asks where the card fields will sit, what the shopper sees if the attempt fails, and whether the basket survives that failure. A checkout that empties the basket on a decline pushes the shopper away. The note can ask for the basket to remain. It cannot promise that the next attempt will be approved.

Support after go-live is the same file, not a new product. When a payment shows one status on the site and another in the dashboard, the technical contact sends the order reference. The reply says which of the two is wrong and what to change: the return address, the server confirmation, or the way the amount is sent. A mismatch that keeps happening is a reason to stay on test keys, even if a few real shoppers have already paid. The merchant is told that in writing. The public page does not turn that conversation into a status board.

Nothing in the folder is a rate card. A merchant who asks for a price receives it, if there is one, after the corridor and the methods are named. A merchant who asks for an approval percentage does not receive one, because this page does not have a number that would be true for the next shop. The reviewer’s job is to say whether the file can be boarded and which path the note should describe. The rest is the acquirer’s decision and the test payment that follows a yes.

What the technical note covers

The note is short on purpose. It names the endpoint or the plugin, the list of methods that were approved, the currency of settlement, and who can see a payment after it is sent. It does not include a public conversion score. It does not include a line that says funds are never held. Holds, reserves and the timing of payouts are lines in the same file, answered for that merchant, not printed as a slogan.

Developers get the fields the hosted page or the API actually expects: amount, currency, order reference, and the return address on the merchant’s site. Card data stays where the chosen setup says it stays. If the acquirer wants the card number to touch only the hosted page, the merchant’s server does not collect it. If a plugin is used, the plugin’s own settings page is where keys are pasted, and those keys are not shown on this site.

The amount is the amount of that order, in the minor unit the note specifies, so a rupee shop and a dollar shop do not guess the decimal. The currency is the code the acquirer named, not a symbol pasted from a theme. The order reference is the merchant’s own id, stable for that attempt, so a refresh does not create a second payment for the same basket. The return address is absolute, on the merchant’s domain, and it is allowed to read the status without trusting a query string that a shopper can edit. If the note says the status must be confirmed by a server call, the browser redirect alone is not the confirmation.

A hosted page has a short list. The merchant’s server creates the attempt, receives a link or a token, and sends the shopper to the page that collects the card. The merchant’s server does not see the card number. When the shopper finishes, the return address loads and the server asks for the status using the order reference. Failure is a status, and the basket is still there for the shopper to try again. The note says how long an unpaid attempt stays open. It does not say that every attempt will succeed.

An API has a longer list, and only a team that will not store the card number should be given it when the acquirer forbids that storage. The note then says the fields that are allowed, the fields that must be rejected, and where the card number is allowed to travel. Logs are part of that sentence. A log that prints the card number is a breach of the note even if the payment succeeded. Test cards, if the acquirer issues them, are named in the note and are not real shopper cards. Live traffic does not use a test card.

A plugin has a settings page inside the store. The note says which store versions are covered and which are not. A theme that redraws checkout can hide the plugin’s fields. The technical contact checks that the card fields, or the button that opens the hosted page, are visible on the theme the shop actually uses. Keys are pasted there by that person. They are not sent to a freelancer in a public ticket. After pasting, the same three checks apply: reference, amount, status.

The note also names who can see a payment after it is sent. That is usually the merchant’s dashboard user, not every staff login on the store. A refund permission can be a different user from a view permission. The note says which is which for this merchant. It does not say that refunds are instant, and it does not say that a refund prevents a dispute. Those timings are in the file for this corridor, after the acquirer has answered them.

Platforms the file can name

A shop already running on a common store system can ask for a plugin. A custom site can ask for the API. The review says which of those two the acquirer will actually support for that merchant. A platform that is not on the list is not invented on this page. WordPress, a custom checkout, and a mobile app are three different jobs, and only the one in the file gets a guide.

The guide, when it is sent, is a list of fields and a test card or a test wallet that the acquirer provides. It is not a public download on this site. The merchant’s developer confirms the webhook returns, the order reference matches, and the amount on the dashboard equals the amount on the order. If those three do not match, the site stays in test. Support for that check is a person who replies to the contact form, not a claim of a desk in every hour of the week. Industries the acquirer may review include shops, travel, digital goods and other models they name. Adult, gaming and similar files are reviewed, not waved through, and some are refused.

• Hosted page, when card fields must not sit on the merchant’s server.
• API, when the merchant’s developers will build the return and the webhook.
• Plugin, when the store system is one the acquirer already allows.

WordPress is named only when the file says the store is WordPress and the acquirer allows a plugin for it. A custom checkout is named when the merchant’s developers will build the return and the server confirmation. A mobile app is a third job: the return is a screen in the app, and the server confirmation is still required. This page does not list every store system on the internet. A system that is not in the file does not get a guide here. If the merchant uses a system the acquirer has not boarded, the answer is to change the path or to stop, not to invent a plugin.

The guide, once it is sent, is private to the technical contact. It repeats the fields, the test instrument, and the three checks. It does not include a price. It does not include a claim that shoppers will skip a password. It does not include a tutorial sold as a separate product. The developer writes back when the test payment is visible, with the order reference. Support for a mismatch is a reply to that note. It is not a promise of a person at every hour. If the three checks fail, live keys wait.

Industries are named in the file the same way platforms are named: only the ones the acquirer will review for this merchant. A retail shop, a travel seller, and a seller of digital goods can all appear. The sentence that follows is the same for each. The model is reviewed. It is not approved because a category was typed on this page. Adult content, gambling, and other models the acquirer treats as sensitive are written plainly if they are the business. Some of those files are refused. The refusal is recorded. The site is not connected anyway.

A shop that sells in more than one language still has one file per site. The language of the checkout is noted so the technical contact knows which labels the shopper will read. The language does not change the card fields. Number and expiry stay number and expiry. A translation of the button does not change who stores the card, and it does not change the return address. If the same catalogue is served on two domains, each domain is written down. The test payment is run on the domain that will take the live payment, not on a copy that will be discarded. A domain that only redirects is not the checkout, and it is not the address written in the note. The note names the page the shopper sees when they pay, and the page they return to after the attempt. Both those pages belong to the merchant.

Questions before a developer starts

How long does a 2d payment gateway integration take?

It takes as long as the site, the platform and the documents require. This page does not print a number of days. Approval by the acquirer comes first. The technical work starts after that yes. A test payment is the last step before live traffic.

Does installing the plugin remove the bank’s check in India?

No. A domestic card payment in India can still be sent through the check the issuing bank asks for. Availability of a shorter card form depends on the acquirer, the network and the rules of that market. It is not a switch in a plugin.

Do you publish a fee for the connection?

No. Another company’s price, a “no approval” line, or a product that claims to skip the bank stays on their site. The cost of the account, if there is one, is in the file after the corridor is known.

Who stores the card number?

The setup in the file says that. A hosted page is chosen when the merchant must not store it. Keys for a plugin are pasted in the merchant’s own admin, not sent in a public chat log.

What should the developer have ready before the note arrives?

The live site address, a staging address if there is one, the store system or the fact that checkout is custom, and a person who can install the path. The business papers are already in the file from the application step. The developer does not need a fee table, and does not need a promise about how many payments will be approved.

What does a finished test look like?

One payment in the test environment whose order reference, amount and status match the order on the site. A failed attempt can be part of the same test if the note asks for it. Live keys come after that match. Real shoppers come after the live payment is watched once.

These answers are the limits of the public page. A merchant who needs the list of papers, the descriptor, or the path for a named site sends the form. The reply is about that site. It does not become a new promise printed here for the next reader.

Send the site

Send the 2d payment gateway integration notes with the site address and the platform you already run. Name, email, the website, and the platform are enough to open the review. Say whether shoppers pay from India or from somewhere else, and name the methods the checkout already shows. The note is emailed from this form. No fee table is attached. A reply that asks for one more paper is still the same review. It is not a new product and not a published timetable.

Name Email Website Platform Request a review