Everyone-friendly specifications

OpenAPI Types

It is a connection method that thinks about and accompanies the people who plan the business, those who are involved in development, those who are in charge of operation, and those who use payment method.
We aim to make it easy and safe to use, and we follow web standards such as RFC and OpenAPI Specification.
As a leading company in the payment industry, GMO Payment Gateway, which has provided payment-related services, is an API that can only be provided.

PG Multi-Payment Service

Everyone-friendly specifications

POINT 1

payment Add means made easy

payment Have you ever wanted to try the means more casually?
It is possible with the OpenAPI type.
POINT 2

Compliant with global standards

It follows all web standards.

software Since the specifications are based on a common understanding of engineers, learning costs are minimized.
Streamline the development process, from design to connection.
POINT 3

Providing safety and security

PCI DSS compliant, providing peace of mind for all customers.
Fraud prevention solutions are also easy to deploy to provide a secure payment environment.

Compatibility with existing connection methods

Customers who are currently using the protocol/module type can easily switch to the OpenAPI type.
Transaction information and registered member data can be used as they are, and shop information and various settings will not change.
In addition, the OpenAPI type can be used in conjunction with existing connection methods.
For example, it is possible to make a flexible transition such as implementing a schedule process to finalize transactions in advance.
The management screen, transaction delivery service, SFTP batch processing, etc. will continue to be available as before.

Feature comparison

	OpenAPI Types	Protocol type	Module type
API reference clarity	◎	○	△
API learning cost	◎	△	△
Ease of embedded development	◎	△	△
Additional costs of payment means	◎	△	△
Security	◎	○	○

APIs that are great for developers

OpenAPIタイプはその名の通り、OpenAPI Specification(OAS)に対応しています。
決済にまつわる複雑なインターフェース仕様に対してもスキーマ駆動開発ができるようになります。
APIリファレンスについても、OASをベースに常に最新の状態のページを提供します。

Furthermore, if you use OpenAPI Generator, you do not need to create troublesome model classes, and you can automatically generate classes that are completely according to specifications.
The APIs provided by the OpenAPI type are not so-called RESTful, but they are designed to be quickly understood by developers familiar with REST APIs.

It also supports idempotency, which can greatly simplify complex implementations to avoid double payment.

OAS compliant

OpenAPI Specification (OAS) compliant

Easy-to-understand API reference

Always up-to-date, intuitive, and easy-to-understand API reference on the web

Supports idempotency

No matter how many times you retry, you will not get a double payment

API Reference

Frequently Asked Questions

Is there an additional cost to use the OpenAPI type?

If you are a PG Multi-Payment Service customer, there is no additional cost. However, if you use additional payment means or anti-abuse solutions, you will be charged an optional fee.
What payment means are available for OpenAPI types?

We are adding more payment available means from time to time. For the latest information, please refer to the API reference for OpenAPI types.
Will existing protocol types and module types be discontinued?

Protocol types and module types will continue to be available, but will be discontinued after April 2029.
It will be possible to continue payment processing even after the end of support, but we recommend connecting with a more convenient OpenAPI type.

For payment method that does not support the OpenAPI type, please use Protocol Type, Module Type, and Link Type Plus. Corresponding payment method will be added sequentially, so please check the following for the latest information.

https://static.mul-pay.jp/doc/openapi-type/