Payment integration is not ready

Open the provider card

Go to Settings / Integrations and review the payment provider that backs the flow you are trying to launch. A provider can exist on the restaurant account but still require onboarding, verification, payout details, or a status refresh before guest-facing payment flows are ready.

Read the card state first:

1. Stripe is ready only when the badge shows Ready. Not connected means no connected account is stored, Action required means Stripe has missing details or requirements, and Under review means Stripe has not enabled charges yet. Use Connect Stripe, Complete setup, and Refresh status from the Stripe card.
2. PAYTR marketplace is used only for supported Turkish reservation payment flows. The card can show Ready, Action required, Blocked, or Not available. Complete Beneficiary name and Turkish IBAN, then select Save payout settings and review Payout readiness.

Do not use one provider as proof that the other provider is ready. Stripe readiness does not make PAYTR payouts ready, and PAYTR readiness does not unlock Stripe card guarantees.

Identify what is blocked

Payment readiness can block guest checkout or settlement even when the experience is editable.

1. Basic reservations that do not collect money or save a card are not blocked by payment readiness.
2. Deposit, Prepay, and the pay-now side of Optional Prepay require a ready Stripe account or an enabled PAYTR marketplace integration. The pay-at-venue fallback in Optional Prepay does not create a paid checkout path.
3. Card required is Stripe-only. Stripe must be Ready, and the restaurant country must support card guarantees before the panel allows the policy.
4. Gift Cards selling requires gift-card-ready payment setup: Stripe details and charges enabled, or PAYTR marketplace enabled with Payout readiness at Ready. If selling is unavailable, Gift Cards shows Selling disabled; existing products and issued cards remain visible, but product edits and public checkout are blocked.
5. Refund, cancellation-fee, and no-show settlement actions depend on the reservation having provider payment or guarantee references. Readiness does not create those references for existing reservations.

Refresh after provider changes

For Stripe, complete the handoff in the Stripe dashboard first. Business details, representative information, bank or payout details, identity verification, terms of service, and additional requirements can all keep the card in Action required or Under review.

After finishing provider-side work, return to Reslify and select Refresh status on the Stripe card. If Stripe still shows Action required, select Complete setup again and resolve the listed requirement group.

For PAYTR, there is no Stripe-style onboarding refresh. Update Beneficiary name or Turkish IBAN, select Save payout settings, and check the Payout readiness message. Blocked or repeated validation errors usually need support review.

Check policy, country, and currency

Provider readiness is only one launch gate. Also confirm:

1. The experience has the intended Payment policy under Settings / Experiences.
2. Deposit mode, group-size conditions, Price per person, service fee, cancellation terms, and no-show rules match the public offer.
3. Card required is not being used for an unsupported country. Current policy support covers Australia, Germany, Türkiye, and the United States.
4. PAYTR is being used only for supported Turkish payment flows. PAYTR-backed gift-card checkout in TRY also requires a valid purchaser phone number.
5. The amount and currency shown to guests match the restaurant's payment integration or merchant country setup before you test live checkout.

When to contact support

Contact support from the panel if:

1. Stripe says onboarding is complete, but Reslify still shows Action required after Refresh status.
2. PAYTR shows Blocked or Not available, or valid beneficiary details do not clear Payout readiness errors.
3. Settings / Integrations looks ready, but public checkout still says payment is unavailable.
4. Gift Cards has a ready provider and an active product, but selling remains disabled or the public gift-card checkout is missing.

Include the restaurant name, provider, exact badge text, any readiness errors, the flow being tested, and the time you completed provider-side changes.