Payments
This section covers the API endpoints for all payment transactions carried out through the system. Payments; Non-3D Secure, 3D Secure and Payment Inquiry are addressed under three main headings.
This document provides only Payments a general framework for the main page. Detailed technical information for each payment type is located on their respective subpages.
Overview of the Payment Flow
Payment transactions proceed with the following basic steps:
A payment request is created
Necessary validations are performed (card, amount, authorization, etc.)
It is transmitted to the bank / card network
A result is received and the transaction status is created
The transaction becomes queryable
Note: For transactions using 3D Secure, the user is redirected to the bank's verification screen.
Payment Types
1. Non-3D Secure Payment
A type of payment carried out directly using card information without 3D Secure verification.
Usage scenarios:
Subscription / recurring payments
Secure card storage infrastructures
Flows requiring fast payment
➡️ For detailed technical integration: Non-3D Secure Payment see the page.
2. 3D Secure Payment
A secure payment method where the cardholder is subjected to an additional verification step by their bank.
Key features:
Verification of the cardholder via SMS / mobile application
Reduction of fraud risk
Compliance with laws and regulations
➡️ For detailed technical integration: 3D Secure Payment see the page.
3. Payment Inquiry
Used to learn the current status of a payment that has been made.
Information that can be queried:
Payment status (successful / failed / pending)
Transaction amount and currency
Bank reference numbers
Creation and update dates
➡️ For detailed technical integration: Payment Inquiry see the page.
Common Concepts
The following concepts are common to all payment transactions:
orderId: The unique order number for the transaction
transactionId: The transaction identifier generated by the system
amount: Transaction amount
currency: Currency (e.g.: TRY)
status: The current status of the transaction
Security and Integration Notes
All requests must be made over HTTPS
API keys must be kept confidential
Card information must never be stored on merchant servers
PCI-DSS compliance should be considered within the scope of integration responsibility
As a next step, you can select one of the payment types to go to the relevant technical detail page.
Last updated