Payment status

yuno.mountStatusPayment(...) rendered a standalone payment result screen for a checkout session, typically shown after the shopper returned from an external redirect. In the unified API this becomes a top-level method on SdkPayments: sdkPayments.transactionStatus(...). It is not part of a Transaction. Like antifraud, it’s a standalone operation, so it lives directly on the SdkPayments instance.

Before you start

Load the unified SDK bundle instead of the legacy one and initialize it as the side-by-side shows: window.Yuno.initialize(...) becomes SdkPayments.initialize(...). Your public API key and the checkout sessions your backend creates do not change (Before you begin).

Side-by-side

const yuno = await window.Yuno.initialize('your-public-api-key')

yuno.mountStatusPayment({
    checkoutSession: 'session-from-backend',
    countryCode: 'CO',
    language: 'en',
    paymentResult(data) {
        console.log('paymentResult', data)
    },
})

const sdkPayments = await SdkPayments.initialize('your-public-api-key')

await sdkPayments.transactionStatus({
    checkoutSession: 'session-from-backend',
    countryCode: 'CO',           // optional
    language: 'en',              // optional
    elementSelector: '#status',  // required
})

What changes

Grouped in the order you edit the code. Renamed: same role, new name. Moved: same value, new owner. Removed: nothing to call. New: no legacy counterpart. The last column is the only thing you have to do beyond the rename.

Initialization and config

Status	Unified	Change	What to do
`window.Yuno.initialize(publicApiKey)`	`SdkPayments.initialize(publicApiKey)`	Renamed	The global is `window.SdkPayments`. As before, `await` it: it resolves to the `SdkPayments` instance.
`checkoutSession`	`checkoutSession`	Moved	Same. Required.
`countryCode`	`countryCode?`	Moved	Now optional.
`language`	`language?`	Moved	Now optional.
(default container)	`elementSelector`	New	Now required: you pass the CSS selector of the element to render into, instead of relying on the SDK’s default container.

Callbacks

Status	Unified	Change	What to do
`paymentResult(data)`	(removed)	Removed	The screen renders the outcome and is display-only. Confirm the result server-side via webhooks or the payments API as the source of truth for fulfillment; inside a `Transaction`, the final status arrives in `onStatus`.

Entry points

Status	Unified	Change	What to do
`yuno.mountStatusPayment({...})`	`sdkPayments.transactionStatus({...})`	Renamed	Top-level method on `SdkPayments`, not on `Transaction`: a standalone operation, not part of a transaction lifecycle. Returns a `Promise<void>`.

onStatus. Receives the final status inside a Transaction.
Get Started. Full integration walkthrough.

Start here

Guides

Listen and take over

API reference

Upgrade from older SDKs

Before you start

Side-by-side

What changes

Initialization and config

Callbacks

Entry points

​Before you start

​Side-by-side

​What changes

​Initialization and config

​Callbacks

​Entry points

​Related

Before you start

Side-by-side

What changes

Initialization and config

Callbacks

Entry points

Related