WerninBill Payment API Documentation
Learn how to integrate WerninBill payment infrastructure into your website, application or online platform using a developer-focused payment architecture.
Explore payment flows, checkout concepts, webhooks, security practices and provider availability before starting your integration.
Getting Started
WerninBill is designed to provide a unified infrastructure layer for businesses integrating supported payment capabilities into their applications.
1. Create Your Merchant Setup
Begin through the self-service onboarding process and configure the payment capabilities available to your business.
2. Review Available Providers
Payment methods and providers depend on merchant eligibility, jurisdiction and current provider availability.
3. Integrate Your Application
Connect your website or application to the applicable WerninBill payment infrastructure and implement the required payment flow.
4. Test Your Integration
Verify your payment flow, status handling and event processing before moving into production.
Payment Integration
A typical WerninBill integration consists of several components working together to create a reliable payment experience.
Payment Request
Your application initiates the appropriate payment flow using the capabilities available to your merchant environment.
Checkout
Customers complete the applicable payment experience through the supported checkout infrastructure.
Payment Status
Your application should correctly handle payment states and avoid relying exclusively on client-side confirmation.
Settlement
Settlement timing and available settlement methods depend on the applicable provider and payment method.
API Concepts
WerninBill is designed around API-oriented payment infrastructure. Your application can use the relevant integration capabilities to create and manage supported payment workflows.
Authentication
Protect integration credentials and never expose private authentication information in client-side code.
Requests
Send payment-related requests from your secure application environment using the integration method applicable to your account.
Responses
Process returned payment information carefully and validate important payment states on your server where appropriate.
Error Handling
Build reliable error handling into your application so temporary failures or rejected payment requests do not create inconsistent order states.
Checkout
Checkout is the customer-facing part of the payment experience. Your implementation should clearly communicate payment status and handle successful, failed and pending transactions appropriately.
Customer Experience
Keep the payment flow simple, clear and consistent with your website or application.
Payment Confirmation
Do not treat a browser redirect alone as definitive proof of payment. Validate payment status through the appropriate server-side mechanism.
Failed Payments
Provide customers with clear feedback when a payment cannot be completed and allow appropriate recovery where supported.
Webhooks and Payment Events
Webhooks can be used to communicate payment-related events to your application where supported by the integration.
Receive Events
Configure your application to receive relevant payment status notifications.
Verify Events
Validate incoming event requests using the security mechanisms provided by the applicable integration.
Handle Duplicates
Design event processing to be idempotent so repeated notifications do not create duplicate orders or actions.
Update Your System
Use verified payment events to update orders, subscriptions or other relevant application states.
Security Best Practices
Protect Credentials
Keep private credentials and sensitive configuration on your server and never expose them publicly.
Use HTTPS
Production payment integrations should use HTTPS to protect data transmitted between your application and payment infrastructure.
Validate Payment Status
Verify important payment states using trusted server-side information before fulfilling an order or service.
Secure Webhooks
Validate incoming webhook requests and implement appropriate replay and duplicate-event protection.
Self-Service Onboarding
WerninBill is designed to let merchants begin through a self-service onboarding process without waiting for traditional manual pre-approval from WerninBill.
Provider Availability
Not every payment method or provider is available to every merchant. Availability may depend on country, business type, transaction characteristics, provider policies and applicable regulations.
Provider-specific requirements and limitations take precedence over general information presented in this documentation.
Production Checklist
Integration Ready
Confirm your application correctly handles successful, failed and pending payment states.
Webhook Ready
Verify webhook security and ensure event processing is idempotent.
Security Ready
Protect credentials, use HTTPS and keep sensitive payment information out of client-side code where applicable.
Business Ready
Confirm that your business and intended payment activity meet the requirements of the applicable provider and jurisdiction.
Need Integration Help?
Review the developer overview or contact WerninBill for integration-related assistance.