Overview
Server-to-Server (S2S) Integration
Also known as Direct API, this integration allows your server to communicate directly with Oceanpayment's API. It is best suited for scenarios that require fully customized payment flows.
- 🔒️ PCI DSS Compliance
- ⚡ Seamless, Fast Payment Integration
- 🎉 Responsive Design Across All Devices



Credit Card Integration
With this integration mode, your server will directly handle, transmit, or process Cardholder Data (CHD). As a result, your system falls under the scope of PCI DSS compliance.
- Your Server:Collect payment information (card number, expiry date, CVV, etc.) from the customer and securely transmit it to Oceanpayment.
- Oceanpayment:Receive payment information, process transactions, return results, and handle settlement with banks and card networks.
Core Compliance Requirements
Choosing this integration means the merchant agrees to fulfill the relevant PCI DSS obligations. Oceanpayment is certified PCI DSS LEVEL 1, but merchants are still responsible for their own compliance.
| Party | Responsibility |
|---|---|
| Oceanpayment | Ensure platform and infrastructure security; maintain PCI DSS-compliant gateway interfaces |
| Merchant | Secure their systems, networks, applications, and handling of CHD; ensure compliance with PCI DSS |
Mandatory Integration Requirements
To ensure a secure and compliant payment environment, merchants using S2S must meet the following requirements:
- No storage of sensitive authentication data
- Complete magnetic stripe data, card verification codes (CAV2/CVC2/CVV2/CID), or PIN blocks must not be stored in databases, logs, or monitoring systems.
- Encrypted Transmission
- All communications between the merchant server and Oceanpayment API endpoints must use strong encryption protocols.
- Minimum: TLS 1.2 or higher. SSL and older TLS versions must be disabled.
- Secure cipher suites must be configured, and weak algorithms disabled.
- Merchants must renew their PCI certificate annually and provide an Attestation of Compliance (AOC).
- External vulnerability scans of all internet-facing systems (web servers, API endpoints, firewalls, etc.)
- must be performed at least quarterly (Q1, Q2, Q3, Q4). A valid report is also required before first go-live.
Compliance Process
- Pre-Assessment:Review this document and evaluate if requirements can be met before integration.
- Technical Integration:Develop integration using Oceanpayment API documentation, following all security requirements.
- Submission & Review:Submit “qualified” ASV reports and signed PCI DSS Level 1 certificates via email for Oceanpayment review.。
Important Notes
- Failure to submit ASV reports or PCI certificates on time may result in service suspension or a requirement to switch integration methods to ensure overall payment environment security.
- This document provides a summary of PCI DSS requirements; official documentation from the PCI Security Standards Council takes precedence.
Next Steps
If you accept these requirements and plan to proceed, contact us via email. Our Technical Account Manager will provide full API documentation and test credentials. For questions regarding compliance or integration, reach us at: techservice@oceanpayment.com.