alt
Unzer
UnzerAI

UnzerAI

The responses generated by AI may include errors.

UnzerAI

Welcome to UnzerAI!

I'm here to help you with questions about Unzer's payment integration, APIs, and documentation.

Ask questions about Unzer and get help with your integration.

How to Ask UnzerAI for Integration Help

Your AI-powered integration companion when you ask the right questions.

Modern AI assistants like Cursor, Claude, and ChatGPT can access and understand our comprehensive Unzer documentation in real-time. By analyzing hundreds of pages, code examples, and integration patterns, they become your personal integration expert available 24/7.

But there’s a catch: the quality of their answers depends entirely on how you ask.

This guide shows you how to ask better questions and get better answers. Learn how to transform vague questions into precise prompts that unlock accurate, actionable guidance and save hours of documentation searching.


The power of asking the right question

Specific questions yield precise answers. The more context and detail you provide, the more targeted and actionable the guidance you’ll receive.

Specificity makes all the difference

Too vague
"How do I integrate payments?"
You'll receive a generic overview instead of the specific guidance you need
Clear and specific
"I'm using UI Components v2 with web components to integrate card payments. How do I handle 3D Secure authentication?"
You'll get precise code examples, exact documentation links, and step-by-step guidance

What makes a good question

Every helpful question should include:

1
icon

Context

Your integration type, programming language, and platform

2
icon

Version

Specify v1 or v2 as they are completely different

3
icon

Use Case

What you are trying to accomplish

4
icon

Specific Question

Clear, focused question about your implementation


Understanding v1 vs v2

icon
Critical: Version Matters

Unzer offers two major versions of Payment Pages and UI Components. They are not interchangeable and have completely different implementations.

Always specify your version when asking questions!

Key differences

Here’s a quick comparison to help you identify which version you’re working with and what to specify in your questions:

Payment Pages

Legacy

Payment Pages v1

  • API: POST /v1/paypage/charge
  • Returns: paymentId
  • Auth: API key
  • Endpoints: Three separate endpoints
Recommended

Payment Pages v2

  • API: POST /v2/merchant/paypage
  • Returns: paypageId
  • Auth: Bearer token
  • Endpoints: Single unified endpoint
  • UI: Modern design
  • Features: Payment method ordering

UI Components

Legacy

UI Components v1

  • Script: static.unzer.com/v1/unzer.js
  • Approach: JavaScript SDK
  • Usage: unzerInstance.Card()
  • Forms: Manual field creation
Recommended

UI Components v2

  • Script: static-v2.unzer.com/v2/ui-components/
  • Approach: Web Components
  • Usage: <unzer-card>, <unzer-paypal>
  • Wrappers: <unzer-payment>, <unzer-checkout>
  • Features: Credentials on File, Address forms

When to specify version

Always specify version when asking about:

  • Payment Pages or UI Components integration
  • Client-side implementation
  • Migration paths

Question templates

Ready-to-use templates you can copy and customize for your specific needs.

Quick reference

A simple formula to structure any Unzer-related question effectively:

I'm implementing [INTEGRATION TYPE] [v1/v2] using [LANGUAGE/SDK] 
for [USE CASE]. How do I [SPECIFIC ACTION]?

By scenario

Real-world examples tailored to common integration situations. Each template includes the context and specificity needed for accurate AI responses:

Initial Integration

Starting a new integration from scratch:

I'm starting a Payment Pages v2 integration using PHP SDK 
for an e-commerce store. I want to accept card and PayPal. 
What's the recommended server-side setup?

Debugging

Troubleshooting errors or unexpected behavior:

I'm using UI Components v2 with web components. 
When I submit <unzer-card>, I get error API.810.100.100. 
My initialization: <unzer-payment publicKey="s-pub-xxx">. 
What's wrong?

Feature Implementation

Adding specific payment features to existing integration:

Using Payment Pages v2 with Java SDK, 
how do I configure recurring payments for subscription billing?

Migration

Moving from one version to another:

I'm migrating from UI Components v1 to v2. 
What's the v2 equivalent of unzerInstance.Card().createResource()?

Effective question examples

Learn from real-world examples that demonstrate the difference between vague requests and precise, actionable questions.

Questions that get great answers

1
icon

Version-Specific Question

I'm using Payment Pages v2. What's the API endpoint for creating an embedded payment page with PHP SDK? Show me the bearer token authentication.

2
icon

Detailed Debug Request

Using UI Components v2, my <unzer-paypal> component doesn't render. I loaded the script from static-v2.unzer.com and console shows no errors. What am I missing?

3
icon

Migration with Context

I'm upgrading from Payment Pages v1 to v2. In v1 I used /v1/paypage/charge endpoint. What's the v2 equivalent and how do I get the bearer token?


Example questions for common scenarios

Ready-to-use question templates for the most common payment integration tasks. Copy, customize, and use these as starting points for your own questions.

Card Payments

I'm implementing one-time card payments using UI Components v2. 
How do I handle the complete flow including 3D Secure, 
payment confirmation, and error handling? 
Show client-side web component code and server-side PHP SDK.

Recurring Payments

I need subscription billing with Payment Pages v2:
- Monthly recurring charges
- Card with stored credentials
- Handle failed payments

How do I structure the initial payment page for recurring use? 
Show PHP SDK code.

Refunds

Using PHP SDK v3.2, how do I:
1. Partially refund a completed charge?
2. Handle the API response?
Show code examples.

Next steps

Ready to start? Here’s your path:

  1. Understand your use case: Define what you want to accomplish (one-time payments, subscriptions, refunds, etc.)
  2. Get a test account: Set up your Unzer test environment
  3. Ask AI which integration fits best: Use the prompting techniques above to get personalized recommendations
  4. Start building: Follow AI guidance with your chosen integration method
icon
Need Human Support?
For additional help, reach out to Sales or Support.

See also