pragmatic play api: Preserve Unfinished Bonus Rounds

A pragmatic play api integration should be tested beyond a successful game launch and a settled spin. One operationally sensitive case is a player leaving during an unfinished slot feature, then returning after their launch session has expired or your platform has entered maintenance. The operator needs to preserve access to the correct game state without inventing outcomes, restarting a paid feature, or treating every missing payout as an integration failure.

This guide focuses on unfinished, in-game features triggered during play—not promotional free-spin campaigns. Exact recovery behavior depends on the title, integration route, and documented provider rules. Use the controls below as acceptance requirements to confirm with your integration partner, not as a claim that every Pragmatic Play title exposes identical recovery methods.

Why unfinished features need their own launch gate

A browser session, a wallet transaction, and a game round have different lifecycles. Closing a tab does not necessarily close the provider's round. Expiring a launch token does not prove that an unfinished feature has expired. A visible animation can also stop after the underlying financial result has already settled.

Confusing these states creates avoidable support and accounting problems. An operator might issue compensation for a payout already credited, direct a player into the wrong game version, or remove a lobby tile while players still need a supported recovery route.

The first control is therefore separation: track what your platform knows about access, financial settlement, and provider round status independently. When one is unknown, record it as unknown rather than inferring it from another.

pragmatic play api: define unfinished-round ownership

Before building recovery screens, establish who owns each decision. Whether access is direct or through an aggregator, obtain written answers from the party responsible for your integration.

Confirm the provider contract

Ask for the documented behavior covering:

• Whether a title can retain an unfinished feature after disconnection.
• Whether recovery occurs through a normal authenticated launch or another supported process.
• Which player, game, currency, and environment identifiers must remain consistent.
• Whether unfinished rounds expire, automatically complete, or require support intervention.
• How round status and settlement evidence can be obtained.
• What happens when a game becomes unavailable before recovery.

Do not assume there is a public pending-round endpoint, a universal timeout, or an operator-controlled resume command. If recovery information is available only through support or back-office reports, include that dependency in your operating procedure.

Keep outcomes with the game system

Your platform should not reconstruct the remaining feature from screenshots, browser storage, or player recollection. It should not simulate missing spins or manufacture a final payout to make a support ticket disappear.

Any discretionary compensation is a separate, authorized ledger action. It must not be represented as the original game's settlement or erase the original unresolved record.

Preserve the identity needed for a safe relaunch

An ordinary-looking relaunch can fail if your integration changes the identity under which the unfinished round was created. Common risk points include account migrations, game identifier remapping, currency switching, and moving traffic between integration routes.

Maintain enough information to investigate the original play context:

• Your stable internal player identifier and its integration-side mapping.
• The provider game identifier and relevant catalog mapping.
• The currency associated with the original play.
• The integration environment and route used.
• Available round and transaction references.
• Launch and interruption timestamps, with a consistent timezone.

Store only necessary data under your retention and access policies. Keep credentials and raw launch tokens out of support records.

If a player selects another currency before returning, do not silently reinterpret the unfinished round in that currency. Follow the documented recovery rules. Where necessary, explain that the original game context must be restored through an authorized path.

A fresh launch credential may be needed, but a new credential should not accidentally create a different player identity. Test those two concerns separately.

Build a reproducible interruption test matrix

Use approved test accounts and a provider-supported test environment. Ask whether feature triggering can be arranged through authorized test tooling; do not assume that a sandbox can force a specific outcome.

For each scenario, capture the initial state, the interruption, the recovery attempt, and the authoritative result.

Interrupt at different feature stages

Test more than one point in the flow:

• Immediately after a feature is awarded.
• After the feature has visibly started.
• Between stages requiring player interaction, where applicable.
• Near the final result, before the client displays completion.
• After financial settlement but before the browser receives confirmation.

These checkpoints help distinguish an unfinished game state from a completed result whose presentation was interrupted. The acceptance condition is correct, explainable recovery—not necessarily replaying every animation.

Change the access conditions

Repeat relevant cases after closing the browser, losing connectivity, allowing the launch session to expire, and signing in on another supported device. Also test an attempted second launch while the first session remains open.

Do not prescribe identical behavior for all titles. Depending on the documented rules, a second launch may be rejected, replace the first session, or follow another supported pattern. Verify that the observed behavior matches the contract and does not leave contradictory settlement records.

For each case, require evidence that no new paid stake was created merely by restoring access, unless the player explicitly initiated new play under the documented flow.

Make maintenance aware of unresolved play

Maintenance planning should distinguish stopping new game entry from resolving existing obligations. A blanket lobby shutdown may prevent further play, but it can also remove the player's only visible route back to an interrupted feature.

Before planned maintenance:

1. Identify unresolved rounds through available provider reports, integration records, or support checks.
2. Confirm whether recovery remains possible during the maintenance window.
3. Document any automatic completion or expiry behavior that could occur during downtime.
4. Assign an owner for exceptions that cannot be resolved before maintenance.
5. Prepare player messaging that accurately describes access restrictions.

Do not keep wagering available where licensing restrictions, self-exclusion, account controls, or other legal obligations prohibit it. For restricted accounts, obtain the authorized settlement or resolution process rather than bypassing those controls to permit a relaunch.

After maintenance, verify unresolved cases against authoritative records. The disappearance of a lobby warning is not proof of settlement.

Give support an evidence-based decision tree

A player reporting “my bonus disappeared” needs investigation, not an automatic refund or an instruction to keep reopening the game.

Support should first determine whether the case concerns unfinished play, interrupted presentation of a settled result, or unavailable game access. Collect the approximate time, game, currency, and relevant internal references without requesting passwords or launch links.

Then follow a controlled sequence:

• Check your ledger for the original stake and subsequent credits.
• Obtain the available provider round status or escalate for it.
• Confirm whether the documented recovery route is currently permitted.
• Give the player one clear next step, or explain that investigation is ongoing.
• Record the resolution and its supporting references.

If financial and game-state records disagree, escalate rather than declaring either record correct without investigation. Avoid promising a payout amount or resolution time that your integration partner has not confirmed.

Set a clear production acceptance standard

Approve launch only when representative interruption tests have documented outcomes, identity mappings remain stable, and support can distinguish recovery from compensation. Any unsupported scenario should have a named owner, escalation route, and explicit launch-risk decision.

GamingAPI provides aggregation through one API, with a seamless wallet and multi-currency support across a catalog of 16,000+ games from 150+ studios. Those platform capabilities do not establish title-specific recovery behavior. Before planning Pragmatic Play access, contact the team to confirm availability for your market, the integration route, and the relevant unfinished-round procedures.

FAQ

Does reopening a game always restore its bonus feature?

No. Recovery depends on the title, original identity and currency, current availability, and documented round rules. Confirm the expected behavior through supported testing.

Should we refund the stake when a player disconnects?

Not automatically. The round may remain recoverable or may already have settled. Investigate first; any compensation should use a separate authorized process.

Can an excluded player relaunch just to finish a round?

Do not bypass exclusion or other account restrictions. Ask the responsible provider or integration partner for the compliant settlement or resolution procedure.