Skip to main content
Acquired

Integration Methods

Payments.How you want.

Four integration paths, one platform. Pick the level of control or customisation you need today.

The integration layer

Four ways.To connect.

From no-code to full API control — clear tradeoffs on compliance, speed and customisation. Pick the path that fits your stack today and graduate up the stack when you're ready.

API

Access to everything via RESTful API.

  • Complete control of the payment journey
  • Dedicated implementation manager support
PCI compliance SAQ-D
Time to live 4+ weeks
Customisation Complete

Components

Pre-built UI components embedded into your site.

  • Configurable display to match your checkout
  • Card, Apple Pay and Google Pay components provided
  • Sensitive card data handled and stored by Acquired
PCI compliance SAQ-A
Time to live 2–4 weeks
Customisation Extensive

Hosted Checkout

Checkout page for all your payment methods.

  • Card, Apple Pay, Google Pay and Pay by Bank in one place
  • Graceful handling of payment failures built in
  • Optimise for conversion or cost by promoting chosen payment methods
PCI compliance SAQ-A
Time to live < 1 week
Customisation Moderate

Payment Links

No-code links to your customer's device.

  • Share via SMS, WhatsApp or Email
  • Includes Card, Apple Pay, Google Pay and Pay by Bank
  • Trigger via the Acquired Hub for true "no-code" payments
PCI compliance SAQ-A
Time to live Immediate
Customisation Limited

Hosted checkout

One integration. Every way to pay.

A user-friendly payment experience across cards, digital wallets, and pay by bank — delivered through a single integration. Pre-built, PCI-light, and live in days.

  • Customise the look and feel of the checkout to match your company branding.
  • Promote payment methods to meet business goals or commercial objectives.
  • Automatic review of card information to improve likelihood of a successful transaction.
  • Recycle failed transactions back through the checkout to retry — no customer drop-off.

FAQ

Picking a path. Common questions.

Which integration method should I start with?

Most teams start with Hosted Checkout — it lives in under a week, keeps you at SAQ-A PCI scope, and supports cards, Apple Pay, Google Pay and Pay by Bank out of the box. Choose Components if you need the checkout inside your own UI, API if you already hold cardholder data, or Payment Links for ad-hoc collections where there is no checkout.

What level of PCI compliance do I need for each method?

Hosted Checkout, Components and Payment Links all keep you at SAQ-A — Acquired handles and stores the sensitive card data on your behalf. The full RESTful API requires SAQ-D because cardholder data passes through your systems. Acquired itself is a PCI DSS Level 1 Service Provider.

Can I mix integration methods?

Yes. One Acquired merchant account spans every method, so you can run Hosted Checkout on web, Components in a native app, and the API for back-office recurring runs — all settling to the same balance with one set of webhooks.

How long does each method take to go live?

Payment Links are immediate from the Hub. Hosted Checkout typically goes live in under a week. Components take 2–4 weeks depending on UX scope. A full API build is typically 4+ weeks including PCI review and testing.

Is there a sandbox or test environment?

Yes. Every integration method has a fully featured sandbox with test cards, simulated 3DS challenges and a webhook receiver. Sandbox keys are issued from the Acquired Hub so you can start integrating immediately, with no card-data risk.

Scope it with. Engineering.

Tell us about your stack, your timeline and your PCI appetite. Our solutions engineers will recommend the right integration path and walk through the docs with you.

  • Sandbox access within one working day
  • Solutions-engineer intro before contracts
  • Plain-language commercials and SLAs

Send us a message

By submitting this form, you agree to our privacy policy. We'll use your details to respond to your enquiry — nothing more.