Andorpay
Back to the blog

Published on · Updated on

Hosted checkout and APIs: choosing your integration

Compare hosted checkout, APIs and plugins for your Andorran business. Choose the customer experience and development your team will maintain.

Two laptops compare an external payment window with payment integrated into the store.

Hosted checkout and API integration can be parts of the same payment solution. Checkout describes where the customer pays; the API defines communication between your application and the payment system. With AndorPay, your server can create a session through the API and send the buyer to the hosted address returned in the response.

For an Andorran business, the useful decision concerns the experience you need and the development your team will maintain. This guide compares those responsibilities without assuming that using an API requires you to build the entire payment interface.

Three concepts that clarify the decision

A hosted checkout is a payment page prepared and served by the payment platform. Your business directs the buyer there with an identified purchase, then uses confirmation to continue the sale.

An API defines communication between systems. It can be used to create that session or retrieve resources. The interface seen by the shopper and the server connection are related decisions, but they are not the same thing.

A plugin adapts the connection to a particular platform. Our WooCommerce plugin connects the order to AndorPay and presents available methods within the normal shopping journey. It can save store-specific development because it already works with its order data and states.

Concept Question it answers AndorPay example
Hosted checkout Where does the customer pay? Page opened from the created session
API How does the application connect? Server creates a session and receives its address
Plugin How does it fit the store? WooCommerce sends and updates the order

What your application does with hosted checkout

It first identifies the purchase and customer. It then requests a session using the required information. The response includes the address the buyer should open. Our REST integration guide documents that journey.

Your application keeps the relationship between the purchase and session. Once it receives a confirmed result, it applies the business action: preparing an order, delivering a resource or enabling access. The payment page handles its part within that sale.

This division lets you use a prepared interface while keeping payment connected to your operation. There is still server work and post-payment handling. Its scope focuses on the connection to your product rather than assuming your team must build every component involved in authorisation.

What remains the merchant’s responsibility

Your business decides what is sold, who buys, what information is required and what will be delivered. In a custom application, these rules need to be represented in data and processes. A payment platform cannot infer a service’s access conditions from a browser redirect.

You also need to explain the state to the buyer. A clear confirmation identifies the purchase and next step. A pending result needs different handling from a decline or a completed sale.

Finally, somebody must answer payment queries. Retain order and payment references so that person can locate the operation. This requirement applies to hosted pages and experiences connected directly to a store’s checkout.

If you already use WooCommerce

Review the plugin before planning independent development. Our journey keeps products and calculations within WooCommerce and uses the order lines and references. You do not need a second AndorPay catalogue for this integration.

Check custom fields, shipping rules and checkout modifications. The plugin covers the documented connection, but tests need to include your particular installation. If another tool receives sales for fulfilment, include that handoff too.

The WooCommerce guide explains the current setup. The purpose of selecting a plugin is to reuse an existing adaptation and verify it in your store. It still needs maintenance and a purchase check after changes to extensions affecting the journey.

If you have a custom application

Choose where the purchase is created and which server communicates with AndorPay. Keep the API key on that server. The browser receives the checkout address, not the secret used to create it.

Your application opens the address returned by the API. Do not build it manually because it belongs to a specific session with its own data and expiry. Using the documented response avoids depending on the internal structure of the URL.

Then connect payment confirmation. Our webhook guide explains notification verification and handling. The language or SDK helps implement communication, while the states of your product remain part of application design.

How maintenance responsibilities change

With a hosted page, your team maintains session creation, the handoff to payment, event handling and delivery. The platform maintains the payment page for that journey. Your connection needs to keep following the API contract in use.

With a plugin, some of that adaptation already exists for the ecommerce platform. Your work focuses on configuration, versions and interaction with other extensions. Updates still need checking against the purchases your business actually handles.

A more customised experience can increase the parts your team maintains. Before committing to it, identify the difference the buyer needs and whether the chosen connection supports it. Additional customisation has value when it solves a specific sales requirement.

What to compare before choosing

The context customers need

Check that buyers recognise the product, amount and merchant. Keep the offer consistent between the sales page and checkout. A change of page is easier to understand when the purchase context remains clear.

Review the return after payment or cancellation as well. Customers should know whether they have finished, are waiting or can try again. That clarity depends on integration and messaging as well as where the form appears.

The work your team can support

A business with its own application and developers can integrate sessions and events into its architecture. A store managed without a technical team may need a prepared connection and help with configuration.

Decide who will maintain the system after launch. That answer helps define a manageable scope and the support required. A demonstration that is quick to build does not explain how a payment issue will be resolved months later.

The operations following payment

Define how payments connect to orders, subscriptions and delivery. If you need renewals, include what happens after the initial purchase. If refunds are required, establish the available process for the connection.

Our documentation states that the current Redsys adapter does not support refunds through this API. Choosing an interface does not make that operation automatically available. The operational procedure belongs in the scope of the payment journey.

Three scenarios to guide your project

A WooCommerce shop with catalogue and shipping. Start with the plugin and check the connection between order data, payment and delivery. Our ecommerce integration guide covers that full journey.

A digital service application. The server creates a session and the confirmed result triggers the access rule. Hosted checkout can be part of this API integration. Identify which account receives the service and how pending attempts are handled.

A service sold after a proposal. A payment link with delivery managed after confirmation may be enough. Before building a custom connection, review the no-code payment-links guide. Technical scope should follow the sale you need to complete.

An example purchase inside an application

Imagine a digital service sold as a one-off purchase. The buyer chooses the product and signs into their account. The server associates that purchase with the customer, creates a session and supplies the payment address to the browser.

The buyer completes authorisation. The application receives the confirmed outcome and activates access for that account. If the browser tab closes before returning, the server confirmation can still establish the result and apply the prepared rules.

The application can then display the purchase state. If a notification is repeated, it recognises the existing operation rather than delivering twice. This example uses an API and hosted page together, with a defined division between payment and the product being purchased.

Keep a clear reference across the handoff

The handoff to checkout should not lose the identity of the purchase. When support receives a question, the order in your application and the payment record must be traceable to each other. Customer name or amount alone is not enough to distinguish similar purchases reliably.

Make that association part of the initial design, alongside the confirmation screen. It helps the developer implement recovery and gives the person assisting customers a practical way to find the result without requesting another attempt.

What to test before launch

Complete a successful authorisation, decline and cancellation in the test environment. Check the purchase-to-payment relationship and the final application state. Add browser closure and a confirmation arriving after the browser returns.

Repeat a notification to establish that the business effect is not duplicated. Inspect the order for a store or access for a service. The integration testing guide describes scenarios and the results worth retaining.

Check the published environment as well: domain, credentials and enabled methods. A working test connection does not establish identical production configuration. Launch includes the agreed checks for each environment and the final journey used by customers.

Frequently asked questions

Does using the API mean building a card form?

No. The documented integration lets you create a session and use the hosted page returned. Your application maintains the relationship to the purchase and handles the confirmed result.

Does hosted checkout remove all development?

It depends on the journey. A custom application still creates sessions and processes confirmation. A dashboard payment link can support a manually managed sale without building that specific server connection.

Can the experience change later?

Any change needs to preserve orders, references and confirmation rules. Define the new journey and test how it replaces or coexists with the previous one before directing customers to it.

What role does an SDK play?

It helps use an API in a particular development environment. It does not determine where the buyer sees the page. Our SDK and virtual terminal integration guide explains its scope.

Define the experience and the work you need to maintain

Tell us your platform, customer journey and who will maintain the connection. We will prepare an AndorPay proposal defining the experience, integration work and assistance.

Explore our virtual payment terminal for Andorra and request an integration proposal. Scope and terms are provided privately.

WhatsApp