Frequently Asked Questions

Success Story with Paywall

Paywall, established in 2022 and based in Turkey, is the country's first payment orchestration initiative in the field of financial technologies. Paywall allows its customers to manage, develop, and expand their entire digital financial processes. It stands out with its PCI DSS Level-1 certified card storage, marketplace modules, recurring payment services, and various algorithms.

You can use Paywall services throughout your online payment processes. You can reduce your integration costs to zero and solve all your processes with institutions that do not provide support services during management.

Paywall does not directly offer services such as Virtual POS. Through Paywall (orchestration), you can access all the services provided by institutions under a single API and manage them all under one roof with advanced algorithms.

How does the integration process with Paywall proceed?

You can complete all your integrations with PayWall through test environments and finish all your tests before going live. For the test environment you need, you can contact our teams via [email protected]

Technical Support

You can access PayWall's technical support teams and operations team 24/7. After sending an email to [email protected], our teams will contact you shortly.

API Support

Paywall services are based on RESTful technology, allowing access from all programming languages you use.

Public and Private keys, what is the difference between them?

Neither the Public nor Private keys should be stored in the client environment. The only information that can be used in the client environment is the TempToken. TempTokens should be obtained from PayWall APIs on the server-side

Public and Private keys do not differ in terms of security. According to PayWall's segmentation rules, some services require communication with Public keys, while others require communication with Private keys.

How many APIs are there, and which ones should I use?

Paywall currently has 4 main APIs, which operate independently from each other as per their respective tasks.

1.⁠ ⁠Understood. If you have any specific questions about PaymentAPI or other aspects of Paywall, feel free to ask!

2.⁠ ⁠⁠Got it! It sounds like PaymentPrivateAPI handles operations such as payment refunds, cancellations, partial refunds, and inquiries. If you have any more details or questions about this API or anything else related to Paywall, feel free to ask!

3.⁠ Understood! It seems CardAPI is responsible for handling credit card storage operations. If you have further questions about this API or any other aspects related to Paywall, feel free to ask!

4.⁠ ⁠⁠MemberAPI handles subsidiary companies and their management within the marketplace framework. If you have more questions about this API or anything else related to Paywall, feel free to ask!

What is Pre-Auth Payment

Pre-authorization" is a mechanism used at the moment of payment to verify the accuracy of the card used and to check the balance. It temporarily holds the funds in the customer's account without actually withdrawing them. For example, if a user named John makes a purchase of 10,000 TL from your system, you can place a pre-authorization on the payment. After completing your internal processes, if there's a possibility of issues (like room reservations, etc.), you can authorize the payment, and upon successful completion, you can issue a "Close Pre-Authorization" command. Until this final command is issued, no funds are withdrawn from John's card; instead, the corresponding amount is temporarily held within the available limit.