RReslifyKnowledge Center

Payments & Revenue Protection

Understand payment readiness

Use the Integrations page to decide whether Stripe, PAYTR, experience payment policies, and gift-card checkout are launch-ready.

6 min/

What readiness means

Payment readiness means the restaurant has the right payment integration for the exact flow being published. It is separate from choosing a policy under Settings / Experiences / Payment policy. A restaurant can configure an experience before the provider is ready, so use readiness as a launch gate before sending guests to a paid flow.

The fastest control point is Settings / Integrations. Review Stripe and, for supported Turkish payment setups, PAYTR marketplace.

The Integrations page showing a ready Stripe connection with a Refresh status action.
The Stripe card shows whether Reslify can create Stripe payment and card-setup flows for the restaurant.

Read the provider card

On Settings / Integrations, check the provider that will be used for the guest flow:

  1. Stripe is ready only when the card shows Ready. That means the connected account has submitted details, has no pending requirements, and can accept charges. Use Connect Stripe when the card is Not connected, Complete setup when it shows Action required, and Refresh status after finishing work in Stripe. Under review means Stripe is still verifying the account.
  2. PAYTR marketplace is available only for supported Turkish reservation payment flows. The card can show Ready, Action required, Blocked, or Not available. Enter Beneficiary name and Turkish IBAN, then select Save payout settings. The Payout readiness summary must be ready before merchant payouts should be treated as operational.

If the restaurant uses PAYTR, do not use the Stripe card as the readiness signal for PAYTR payouts. If the restaurant uses Stripe, do not use PAYTR readiness as proof that Stripe card guarantees are available.

Readiness and experience policies

Experience payment policies define what the guest must do during booking. Provider readiness defines whether Reslify can actually collect the payment or save the card.

Use these matches before publishing:

Deposit

The restaurant needs a ready Stripe account or an enabled PAYTR marketplace integration for paid reservation checkout. Also confirm the deposit amount, fixed or per-guest mode, and any group-size condition in the experience. PAYTR payout readiness is still operationally important for settlement, but reservation checkout is gated by the enabled PAYTR integration.

Prepay

The restaurant needs a ready Stripe account or an enabled PAYTR marketplace integration. The Price per person must be greater than zero, and any service fee should be reviewed before launch. PAYTR payout readiness is still operationally important for settlement, but reservation checkout is gated by the enabled PAYTR integration.

Optional Prepay

Provider readiness is required for guests who choose to pay now. Guests who choose the pay-at-venue fallback do not create the paid checkout path.

Card required

This is Stripe-only. Stripe must be ready, the restaurant country must support card guarantees, and the guest saves a card guarantee rather than paying now. PAYTR readiness does not unlock this policy.

Gift cards

Gift-card selling is enabled only when the payment setup is gift-card ready: Stripe details and charges enabled, or PAYTR marketplace enabled with Ready payout readiness. If selling is disabled, existing products and issued cards remain visible, but product edits and public checkout are blocked.

If provider readiness is incomplete, the experience may be configured but should not be treated as launch-ready.

Update status after provider changes

For Stripe, use Refresh status after completing onboarding, changing business information, updating payout details, or resolving requirements in the Stripe dashboard. If the card still shows Action required, complete the missing Stripe requirements before launch.

For PAYTR, update Beneficiary name or Turkish IBAN, select Save payout settings, and review the Payout readiness message. If the card still shows Action required or Blocked, resolve the listed errors or contact support with the restaurant name.

Launch checklist for paid flows

Before publishing a paid flow:

  1. Confirm the correct provider card in Settings / Integrations.
  2. Review the experience Payment policy and cancellation terms.
  3. For Card required, confirm Stripe readiness and country support.
  4. For gift cards, open Gift Cards and confirm selling is not disabled.
  5. Make a test booking or gift-card purchase through the public portal.
  6. Confirm the reservation, purchase, payment, or guarantee details appear in the panel.
  7. Confirm guest-facing text explains the amount, saved card, refund terms, or checkout path clearly.

Related guides