Payment credentials that aren't locked to one provider

When credentials belong to a provider, so does your optionality.

Stored payment credentials are what make repeat and remote payments possible — and they usually live inside a single provider's environment. That shapes more than architecture: it shapes how freely a business can change provider, and whether a change of provider reaches the customer at all.

• Credentials sit inside one provider's environment

  Payment credentials are usually held within the environment of a single payment provider.
• Repeat payments depend on a stored credential

  Remote and repeat payments rely on a credential that can be reused reliably.
• Ownership shapes optionality

  Where the credential lives shapes how easily a business can change provider.
• Provider changes can reach the customer

  A change of provider can reach the customer if credentials cannot move with the business.

A credential that belongs to your payment architecture.

A Universal Token is a secure digital reference that stands in for a customer's card number. The reference is held and managed by the Juno platform, so the credential belongs to the payment architecture rather than to one provider integration.

Universal Token provides a common credential layer across supported Juno payment workflows, working with the payment providers Juno supports rather than with every provider in the market.

Protect, use, switch, extend.

The credential layer of the Juno platform.

Applications connect to Juno; Juno holds the credential; supported payment providers process the payment; the card networks authorise it. Universal Token is the layer that keeps the credential constant while everything downstream can change.

• Acquiring

  Where the payment is accepted and settled.
• Settlement

  How funds arrive and are accounted for.
• Reconciliation

  How each transaction is matched back to a payout.
• Portal

  Where estates see and manage payment activity.
• Intelligence

  How payment data becomes reporting and insight.
• Universal Token

  The credential layer these capabilities share, held in the Juno platform.

Move provider without asking customers for their card again.

Juno Universal Token allows a business to change supported payment providers while retaining reusable stored payment credentials, removing the need to recollect those credentials solely because the PSP changes. Which providers and workflows apply to a specific estate is confirmed as part of scoping.

Virtual card (VCC) processing in supported Juno workflows.

A large share of hospitality revenue arrives as a virtual card. When a guest books through an online travel agency such as Expedia, the agency issues a single-use virtual card number that the hotel charges for the stay. Those credentials have to be captured, stored securely and presented again when a booking is amended, extended or settled in stages.

Juno Universal Token holds that virtual card credential as a platform-held reference and presents it through supported Juno payment workflows, so the payment is repeatable without exposing the underlying card details within the payment workflow. Universal Token provides a common credential layer across supported Juno payment workflows.

• Virtual card (VCC) processing

  OTA-issued virtual card credentials are held as a Universal Token and presented through supported Juno payment workflows, without exposing the underlying card details within the payment workflow.
• Repeatable by design

  A platform-held credential can be presented again when a booking is amended, extended or settled in stages.
• Platform-held reference

  The credential belongs to the payment architecture, not to one provider integration.
• PCI Level 1 secure

  Universal Token operates within a PCI Level 1 secure environment.

See how Juno Universal Token fits your payment environment.

Tell us which systems and payment providers you run today, and we'll walk through where a platform-held credential changes what's possible.