Skip to main content
DELETE
/
api
/
v1
/
payments
/
stripe
/
projects
/
{project_id}
/
config
Delete Stripe Configuration
curl --request DELETE \
  --url https://api.devkit4ai.com/api/v1/payments/stripe/projects/{project_id}/config \
  --header 'Authorization: Bearer <token>'
{
  "detail": [
    {
      "loc": [
        "<string>"
      ],
      "msg": "<string>",
      "type": "<string>"
    }
  ]
}
Deactivate the Stripe payment configuration for a project. This marks the configuration as inactive but does not delete existing subscriptions or payment records.

Authentication

This endpoint requires developer authentication via OAuth2 Bearer Token. You must own the project.

Path Parameters

project_id
string (UUID)
required
The unique identifier of the project

Example Request

curl -X DELETE "https://api.devkit4ai.com/api/v1/payments/stripe/projects/550e8400-e29b-41d4-a716-446655440000/config" \
  -H "Authorization: Bearer {developer_jwt}"

Response

Returns 204 No Content on success.

What Gets Deactivated

When you delete a Stripe configuration:
ItemAction
API CredentialsMarked as inactive, no longer usable
Webhook SecretNo longer validates incoming webhooks
Existing SubscriptionsRemain active in Stripe
Payment HistoryPreserved for records
Important: Deleting the Stripe configuration does NOT cancel active subscriptions. Users will continue to be charged until you manually cancel subscriptions in Stripe.

Before Deleting

1

Cancel Active Subscriptions

Cancel all active subscriptions through Stripe Dashboard or API to stop billing.
2

Notify Users

Inform subscribers about the service discontinuation.
3

Export Data

Download payment and subscription records if needed.
4

Delete Configuration

Call this endpoint to deactivate the configuration.

Reactivating Payments

To re-enable payments after deletion, create a new configuration:
curl -X PUT "https://api.devkit4ai.com/api/v1/payments/stripe/projects/{project_id}/config" \
  -H "Authorization: Bearer {developer_jwt}" \
  -H "Content-Type: application/json" \
  -d '{
    "test_secret_key": "sk_test_..."
  }'

Error Responses

StatusDescription
401Unauthorized - Invalid or missing authentication
403Forbidden - You don’t own this project
404Project or configuration not found

Authorizations

Authorization
string
header
required

The access token received from the authorization server in the OAuth 2.0 flow.

Path Parameters

project_id
string<uuid>
required

Response

Successful Response