---
title: "Create embedded Google Ads payment setup"
method: POST
path: "/api/apps/{app_id}/google-ads/billing/payment-setup-embedded"
---

# Create embedded Google Ads payment setup

`POST /api/apps/{app_id}/google-ads/billing/payment-setup-embedded`

<Info>This API is in beta. Endpoints, fields, and behavior may still change, so avoid depending on it in production.</Info>

Starts the card-saving flow for rendering inside your own page, rather than sending a person to a Stripe-hosted page.

This is the embedded counterpart to [Create Google Ads payment setup](/api-reference/create-google-ads-payment-setup). It takes no body, because there is no return trip to configure: you mount Stripe's embedded checkout with the `client_secret` and poll [Get Google Ads billing status](/api-reference/get-google-ads-billing-status) to see when the card lands. Nothing is charged here.

Prefer the hosted flow unless you are actually building the form. It hands you one URL to give a person, where this hands you a token you still have to render Stripe's component around.

<Note>Base44 never accepts card details through this API, and neither should you. This endpoint only produces the page a person fills in.</Note>

<Note>This endpoint accepts a personal API key. Workspace API keys are not authorized for it and are rejected with a 403.</Note>

## Path parameters

- `app_id` string, required — ID of the app whose Google Ads campaigns to manage.

## Response `200`

The token for mounting Stripe's embedded checkout.

- EmbeddedPaymentSetupSession — A Stripe Checkout session for saving a card inside your own page.
  - `client_secret` string, required — Token that mounts Stripe's embedded checkout in a browser. It is meant for client-side use and is scoped to this one session, so it is not a secret key, but it does let whoever holds it complete this card setup.
  - `session_id` string, required — Stripe's ID for the session.
  - `publishable_key` string, required — Base44's Stripe publishable key, which the embedded checkout needs. It is public by design.

## Other responses

- `401` — Missing or invalid credentials.
- `403` — You don't have access to this app, the app does not exist, or you used a workspace API key. A missing app and an app you cannot reach are deliberately the same answer.

## Changes

- **2026-09-03** `6ad855bf424f` — 1 info
  - endpoint added

[Change history](https://skmtc.dev/idealspot/apis/base44-app-management-api/changes/api/apps/:app_id/google-ads/billing/payment-setup-embedded/post.md)

---

[API](https://skmtc.dev/idealspot/apis/base44-app-management-api.md) · [All operations](https://skmtc.dev/idealspot/apis/base44-app-management-api/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/idealspot/base44-app-management-api/revisions/6ad855bf424f/schema)