Migrating from RPG & SecurePay

If your website or systems have been taking online card payments through Borgun — or through Teya before the new platform — this section is for you. You may know the old setup as "the Borgun payment page", SecurePay, RPG, the Borgun Payment API, B-Gateway or the Ticket API; whichever name you recognise, find the row below that describes how you take payments today. That is your guide.

Do you take payments on behalf of other merchants?
Platforms, plugins and agencies that migrate several merchants at once have their own section, including how to obtain credentials for existing merchants without re-onboarding them.

What is changing

Teya's legacy online payment systems — the Borgun payment page (SecurePay), the Borgun payment API (RPG), the B-Gateway web service and the Ticket API — continue to work as normal today, and nothing changes for you right now. Onboarding to those systems will stop soon, and they will be retired in early 2027. Before then, your integration needs to move to the new Teya online payments platform.

The right route depends on your current setup. The effort varies from nothing at all (if you sell through a partner platform) to a small development project, typically days including testing. Every path below is live today and can be started immediately.

Find your path

If more than one row applies — a webshop checkout and payment links, for example — migrate each with its own guide.

How you take payments todayTypical signsYour migration path
Customers are redirected to a SecurePay payment page Your site posts a form to securepay.borgun.is; your developer set up a "payment form post" with a checkhash SecurePay → Hosted Checkout — the like-for-like path: lowest effort, same redirect experience for your customers
The SecurePay payment form is embedded in your own checkout displaymode=iframe in your integration; customers pay without leaving your site SecurePay → Embedded Components — keeps the payment form on your page (Hosted Checkout can't)
You redirect to SecurePay but want an on-site checkout You care about checkout conversion and branding, or want Apple Pay on your own page SecurePay → Embedded Components — read its "which is right for you" section first
Your systems call the RPG payment API directly Code calling /api/payment on borgun.is; a private access token; your own 3D Secure (MPI) integration RPG → Embedded Components
Your systems call the B-Gateway web service SOAP/XML requests such as getAuthorization to gateway01.borgun.is; a B-Gateway username and password; card numbers or virtual card numbers (9910…) reach your own servers; often no 3D Secure. Also known as BGateway or Greiðslugátt B-Gateway → Embedded Components: card numbers no longer pass through your systems
You create payment URLs and send them to customers Payment links made in advance for email, phone or invoice orders (the Ticket API) Ticket API → Payment Links — often no code at all; links can be created in the Business Portal
You store customers' cards or take recurring payments Multi-use tokens (tm_…) or virtual card numbers (16 digits starting 9910); subscriptions or instalments charged when the customer isn't present Migrate your one-off payments first with the row that matches you, then follow Stored cards & recurring — your customers' saved cards carry over without re-entering a card
You sell through a partner platform A booking system, webshop provider or till system built the integration — you never did The preparation is managed for you by your platform provider. Watch for their instructions — you may need to reconnect your store or sign in again when the switch happens. If in doubt, ask them or your Teya contact.
You use a Teya plugin for WooCommerce or Shopify A Teya or Borgun plugin installed in your shop admin Install the current Teya plugin and connect it to your Teya account — see Connect with e-commerce platforms and Set up and connect your plugin to Teya in the Help Centre. Watch for instructions from Teya; you may need to sign in again when your store switches over.
Planning to use an AI coding assistant?
It can save your developer a lot of time on this migration. Migrate with an AI assistant has ready-made prompts for identifying your legacy integration, building the migration and raising questions with Teya, plus a single downloadable file containing this whole section for the assistant to read.
Not sure which row is you?
Ask your developer, or whoever built your site, three questions. "Where does the customer type their card number?" — a Teya/Borgun page means redirect; a frame inside your page means embedded; your own form means a direct API (RPG or B-Gateway). "Do any of our systems call an address containing borgun.is?" "Do we send JSON to /api/payment, or XML such as getAuthorization?" — JSON is RPG, XML is B-Gateway. Between them, the answers place you in one row. Still unsure? Contact your Teya account manager and we'll look at your setup together.

What you gain

This is more than a platform change. The new platform was built from the ground up and removes the most dated parts of the legacy integrations.

More completed payments — merchants on the new platform generally see higher conversion, thanks to modern 3D Secure with fewer challenges, less checkout drop-off, and higher authorisation rates on network tokens for stored cards
A smoother checkout — a clean, trusted payment flow with built-in 3D Secure, card retries without losing the sale, and wallets like Apple Pay
Flexibility in how you integrate — ready-to-use Shopify and WooCommerce plugins, a hosted checkout page, or embedded components on your own site
Payment confirmations that can't get lost — every successful payment is confirmed server-to-server with a signed webhook, whether or not the customer makes it back to your site
Less security and compliance complexity — Teya handles the sensitive parts of the payment flow; card data never touches your servers
One Teya setup across channels — online payments in the Teya app and Business Portal alongside the rest of your business, including refunds without a developer
A platform that keeps evolving — continued investment in checkout features, payment methods and ecommerce capabilities

Migration guides

Every guide has the same shape: a short first part for the business owner — why, what you gain, what to send your developer — and a developer guide with how it works before and after, a table of what replaces what, and the migration steps.

SecurePay → Hosted Checkout

The like-for-like path

One server-side call replaces the signed form post; your customer still pays on a Teya page and comes back to your site.

Lowest effort

SecurePay → Embedded Components

Keep the checkout on your site

For iframe integrations, or for anyone who wants an on-site checkout with Apple Pay. Includes a Hosted Checkout comparison.

Some code

RPG → Embedded Components

For direct API integrations

Replace /api/payment and your MPI calls with a checkout session and a component; 3D Secure is handled for you.

Some code

B-Gateway → Embedded Components

For SOAP/XML integrations

Replace getAuthorization, your card form and any 3D Secure flow with a checkout session and the Checkout component; save cards for subscriptions and charge them by API.

Some code

For pre-created payment URLs

Create links in the Business Portal or by API, get paid by webhook.

No code option

Stored cards & recurring

Do this after your one-off payments

Your customers' saved cards move to the new platform without anyone re-entering a card. Four phases, no bulk conversion on your side.

Reference: what replaces what

Whichever path you take

Test first. Every guide walks through a full rehearsal in Teya's staging environment with test cards before any real traffic moves.
Nothing switches until you're ready. Your current integration keeps working in parallel while you build and test, and for a safety window after you switch.
Help is a message away. Your Teya account manager can set you up with a development store today — that is step one of every path.
Need help?
Contact your Teya account manager, or reply to the email that pointed you here, to get a development store and a named contact for your migration. For integration questions, see Support.

Next steps