Endpoint Details
PUT
/api/v0/payment-links/{id}
Idempotency: Supported (recommended for all update operations)
Authentication
All requests require API key authentication using the following headers:x-client-key
: Your application’s client keyx-client-secret
: Your application’s client secret
Idempotency
The endpoint supports idempotency to prevent duplicate updates:idempotency-key
: Include a unique UUID v4 in the header- Subsequent requests with the same key return the original response
- Keys expire after 24 hours
Path Parameters
Unique payment link identifier
Example:
Example:
"pl_01HZXK8M9N2P3Q4R5S6T7U8V9W"
Request Parameters
All parameters are optional for updates. Only provided fields will be modified.Basic Information
Display title for the payment link (3-100 characters)
Example:
Example:
"Updated Premium Subscription"
Detailed description (max 500 chars, supports markdown)
Example:
Example:
"Enhanced premium features with new benefits"
Cover image URL for the payment link
Example:
Example:
"https://example.com/images/new-cover.jpg"
Pricing and Configuration
Fixed amount for the payment link (minimum 0.01)
Example:
Example:
39.99
Payment currency
Values:
Example:
Values:
"usdc"
, "eurc"
Example:
"eurc"
Whether to allow quantity adjustment
Example:
Example:
false
Whether to allow mobile payment methods
Example:
Example:
true
Product Configuration
Array of products to include in the payment link
Type: Array of
Note: This replaces the entire product list
Type: Array of
PaymentLinkProduct
objectsNote: This replaces the entire product list
Whether the payment link is for all products
Example:
Example:
true
Tax and Collection Settings
Whether to collect tax on the payment
Example:
Example:
true
UUID of the tax configuration to apply
Example:
Example:
"123e4567-e89b-12d3-a456-426614174005"
Whether to collect customer address
Example:
Example:
true
Payment Limits
Whether to limit the number of payments
Example:
Example:
true
Maximum number of payments allowed (minimum 1)
Example:
Example:
500
Advanced Settings
Custom fields for additional data collection
Example:
Example:
{"updated_field": "new_value"}
Expiration date for the payment link (ISO 8601 format)
Example:
Example:
"2025-12-31T23:59:59Z"
Request Examples
Response Format
Success Response (200 OK)
Use Cases
1. Price Updates
Update payment link pricing based on market conditions or promotions.2. Content Management
Keep payment link descriptions and branding current.3. Configuration Changes
Modify payment settings and collection requirements.Best Practices
- Use idempotency keys for all update operations
- Validate data before making API calls
- Handle partial updates gracefully
- Monitor payment link performance after changes
Related Endpoints
- Create Payment Link - Create new payment links
- List Payment Links - Get payment links with filtering
- Fetch Payment Link - Get specific payment link details