Migrating from RPG

This guide is for partners and merchants who are currently integrated with RPG (Borgun Payment API) and are moving to the new Teya ecommerce stack. It walks through the integration options available and maps each RPG capability to its replacement.

```admonition icon: fas fa-key title: New credentials content: Every integration below authenticates with new ecommerce credentials, created per store in the Business Portal — see Authenticate. ```

Choose your integration

There are two ways to take payments on the new stack: Embedded Components and direct API integration. We highly recommend Embedded Components.

Embedded Components (highly recommended)Direct API
Integration effortMedium — drop pre-built UI components into your checkout pageHigh — you build the payment UI and orchestrate every call yourself
Look and feelSeamlessly blends into your website, with customisable stylingFully yours to build
3D SecureHandled for youHandled for you on the transaction flow
Fraud protectionEnhanced fraud protection built in — the components collect device and behaviour signals that strengthen risk decisions on every paymentStandard fraud checks only

With Embedded Components you keep full control of your checkout page while the components handle card capture, 3D Secure and Apple Pay for you. See the Embedded Components overview to explore what they look like.

Use the direct API only where components have no equivalent, such as collecting merchant-initiated payments on stored cards.

What replaces what

The table below covers the RPG operations documented in the RPG API reference and where each one lives on the new stack.

RPG capabilityRPG endpointsNew integration
Authentication HTTP Basic with a private key Authenticate — OAuth client credentials, issued per store, exchanged for a bearer access token.
Card payments (incl. 3D Secure) POST /api/payment
POST /api/mpi/v2/enrollment
POST /api/mpi/v2/validation		 Embedded checkout or card components — 3D Secure is handled for you, with no separate enrollment or validation calls.
Tokenisation POST /api/token/single
POST /api/token/multi		 Card on File — save a customer's payment method during a payment or with a zero-amount account verification.
Apple Pay POST /api/payment with a wallet token Embedded Apple Pay component — Apple Pay support without hosting your own wallet integration.
MIT / collection payments POST /api/payment with a multi-use token Charge a Saved Payment Method — a merchant-initiated transaction on a stored card via the direct API.
Refunds, captures & cancellations PUT /api/payment/{id}/refund
PUT /api/payment/{id}/capture
PUT /api/payment/{id}/cancel		 Payment Actions — capture with POST /v1/transactions/{id}/capture and refund with POST /v3/refunds. There is no separate cancel: a refund on an uncaptured payment reverses the authorisation, replacing the RPG cancel.
Payment notifications GET /api/events/{eventId} Webhooks — signed notifications pushed to your platform in real time.
```admonition icon: fas fa-id-card title: RPG tokens: don't re-collect cards content: Tokens minted on RPG cannot be charged on the new platform as they are — but your customers never need to re-enter a card. Teya imports your stored cards and each legacy token upgrades itself on its first charge. See Migrating stored cards & recurring payments. ```

Next steps