Introduction

Introduction

Welcome to the Precium Server-to-Server (S2S) Payment Integration documentation. This comprehensive guide provides everything you need to integrate Precium's payment processing capabilities directly into your application infrastructure.

‍

Who Is This Documentation For?

This documentation is designed for:

• Payment Service Providers (PSPs) building payment solutions for their merchant networks
• Enterprise Development Teams implementing custom checkout experiences
• Technical Integrators requiring direct API access with full control over the payment flow
• Platform Engineers embedding payments into SaaS applications, marketplaces, or mobile apps

‍

Prerequisites

Before beginning your integration, ensure your organisation meets the following requirements:

‍

‍

Documentation Overview

This documentation suite consists of seven interconnected guides:

‍

Core Documentation

‍

Supporting Documentation

‍

Supported Payment Scenarios

Precium S2S supports a wide range of payment scenarios to meet diverse business needs:

‍

Customer-Initiated Transactions (CIT)

• Standard Payment with 3DS — Card-present transactions with Precium-managed 3D Secure authentication
• Zero Authorization — Validate cards without charging (card-on-file verification)
• Pre-Authorization — Reserve funds for later capture (hotels, car rentals, etc.)
• External 3DS (MPI) — Use your own 3D Secure provider with Precium processing

‍

Merchant-Initiated Transactions (MIT)

• Recurring Payments — Subscription billing using stored tokens
• Instalment Payments — Split payments over time
• Unscheduled MIT — Variable-amount charges (usage-based billing)

‍

Post-Transaction Operations

• Full and Partial Captures — Capture authorized funds in full or in parts
• Full and Partial Refunds — Return funds to customers
• Voids — Cancel transactions before settlement

‍

Integration Architecture

flowchart LR
    YS[Your Server] -->|API calls| PA[Precium API]
    PA -->|Routes| CN[Card Networks]
    YS <-->|3DS Flow| YF[Your Frontend]
    PA -->|Real-time events| WH[Webhooks]

‍

Key Integration Points:

1. Server-to-Server API — Create clients, purchases, and manage transactions
2. Direct Post URL — Securely submit card data (PCI-compliant endpoint)
3. 3DS Handling — Redirect customers for authentication challenges
4. Webhooks — Receive real-time transaction status notifications

‍

API Quick Reference

‍

Base URL: https://gate.reviopay.com/api/v1/

‍

Authentication: Bearer token in Authorization header

‍

Getting Started

Recommended Learning Path

1. Start with the Quick Start Guide to complete your first test transaction
2. Review the S2S Integration Guide for your specific payment scenarios
3. Review technical reference documentation for easy evaluation of all core API requests
4. Implement webhook handling using the patterns in the Integration Guide
5. Reference Code Examples for production-ready implementations
6. Complete the Testing Checklist before going live

‍

Sandbox Environment

All development and testing should be performed in the sandbox environment using test card numbers.

‍

‍

Note: Sandbox and production use the same base URL but different API credentials.

‍

Security Considerations

Integrating with Precium S2S requires adherence to strict security standards:

• PCI DSS Compliance — Your organisation must maintain SAQ-D certification
• API Key Security — Never expose API keys in client-side code or logs
• Webhook Verification — Always validate webhook signatures in production
• HTTPS Only — All communication must use TLS 1.2 or higher
• Token Storage — Store payment tokens encrypted at rest with access controls

‍

Support Resources

‍

Next Steps

Ready to begin? Start with the Quick Start Guide to process your first test transaction in minutes.

‍

For questions or support, contact us at support@precium.com.