Payments
The Omnitron module where the payments and their configurations are stored. POS, Bank,Card, CardType, MultiCurrencyCard, BinNumber, Installment, PaymentOption and BankAccount models are in the payments application. Virtual POS settings to be used on webshop and mobile platforms, management of bank settings, defining new card types and management of their settings, payment options such as credit-card, cash-register etcCredit and debit card settings can be managed using different checkout providers through the payments application.
POS
Stores the settings of the virtual POS you will use on your website or mobile application. It can be accessed from the Sales Channels > Payment Management > Add/Edit POS Integration menu on the Omnitron panel.
Potential Responses
201 Created
400 Bad Request
404 Not Found
405 Method Not Allowed
406 Not AcceptableGET POS
Retrieves attribute values from the POS table. Gets the filter parameters with {omnitron.payments.resources.filters.PosFilter} in PosFilter as query parameters. Supports pagination by inheriting ViewSet from ListModelMixin with query parameters of page=X and limit=Y.
Path: /api/v1/pos/
Filters: Filtering can only be done with channel, id and modified_date.
Example: ?channel=1
Response
POST Create POS
Adds a new record to the POS table. Verified with PosSerializer. Returns HTTP400 if data is not available. Returns HTTP406 if there is an error or incompatibility at the service layer during the registration process.
Path: /api/v1/pos/
Response
The success response status is HTTP201 and the response body contains the generated POS information HTTP400 and HTTP406 response statuses mean that the POS object was not created.
Errors
GET POS Detail
Retrieves the object of the corresponding primary key from the POS table. If it cannot find the object, it returns HTTP404.
Path: /api/v1/pos/{id}/
Returns POS information with the provided ID.
Response
Successful response status is HTTP200 and response BODY is the details of the object.
DELETE POS
Path: /api/v1/pos/{id}/
Permanently deletes POS with the provided ID.
Response: Only returns status 204 in response
PATCH-PUT Update POS
Path: /api/v1/pos/{id}/
POS information with the provided ID is updated.
Request
Response
Errors
GET Schema Structure
Path: /api/v1/pos/schema/
Returns the schema structure for the POS endpoint.
Bank
Permits bank definitions on Omnitron. It can be accessed from the Sales Channels > Payment Managements > Banks menu on Omnitron.
Potential Responses
GET Banks
Path: /api/v1/banks/
Returns the recorded banks in Omnitron.
Response
Filters
Filtering can only be made with channel, ID and modified_date.
/api/v1/banks/?channel=1
Response
POST Create Bank
Path: /api/v1/banks/
Adds a new record to the Bank table. It is validated with BankSerializer. If the data is not suitable, it returns HTTP400. If there is an error or non-compliance in the service layer during the recording process, it returns HTTP406.
Response
HTTP 200
Errors
GET Bank Detail
Path: /api/v1/banks/{id}/
Returns bank information with the provided ID.
Response
DELETE Bank
Path: /api/v1/banks/{id}/
Permanently deletes banks with the provided ID.
Response
Only returns status 204 in response.
PUT-PATCH Update Bank
Path: /api/v1/banks/{id}/
Permits changes to banks with the provided ID.
Response
Errors
POST Bulk Bank Creation
Path: /api/v1/banks/bulk_create/?channel_id={channel_id}
Permits the bulk creation of banks with the CSV file. It is mandatory to provide channel ID as a query parameter. The fields in BankSerializer must be present in the CSV file. The logo must be expressed within the URL.
Response
Card Type
Used for the type identification of the cards to be defined on Omnitron. It can be accessed from the Sales Channels > Payment Management > Card Types menu on Omnitron.
Potential Responses
GET Credit Card Types
Path: /api/v1/card_types/
Returns the card types registered on Omnitron.
Filters
Filtering can only be done with channel, ID and modified_date.
/api/v1/card_types/?channel=1
Response
GET Credit Card Type Detail
Path: /api/v1/card_types/{id}/
Returns card types with the provided ID.
Response
DELETE Credit Card Type
Path: /api/v1/card_types/{id}/
Permanently deletes card types with the provided ID.
Response
Only returns status 204 in response
PUT-PATCH Update Credit Card Type
Path: /api/v1/card_types/{id}/
Updates card types with the provided ID.
Response
Errors
POST Create a New Card Type
Adds a new record to the CardType table. Validated with CardTypeSerializer. Returns HTTP400 if data is not available. Returns HTTP406 if there is an error or incompatibility at the service layer during the recording process.
Path: /api/v1/card_types/
Response
HTTP 200
Response
HTTP 400
Card
Used to define and process cards that can be used in sales channels on Omnitron. Creating a card firstly requires the creation of a card type, POS and the bank to which it will be linked. It can be accessed from the Sales Channels > Payment Management > Card Settings menu on the Omnitron panel.
Potential Responses
GET All Credit Cards
Path: /api/v1/cards/
Returns all cards registered in the system.
Filters
Location: Omnitron.payments.resources.filters.CardFilter
Filtering can be performed with all fields available in the Card model.
Example: ?name=Bonus&bank=2
Response
GET Card Detail
Path: /api/v1/cards/{id}/
Returns card information with the provided ID.
Response
PUT-PATCH Update Card
Path: /api/v1/cards/{id}/
Updates the card information with the provided ID.
Response
Response / 400
Response / 406
POST Create Card
Adds a new record to the card table. Verified with CardSerializer. Returns HTTP400 if data is not available. Returns HTTP406 if there is an error or incompatibility at the service layer during the registration process.
Path: /api/v1/cards/
Response / 201
Response / 400
Response / 406
DELETE Credit Card
Path: /api/v1/cards/{id}/
Permanently deletes cards with the provided ID.
Returns status 204 in response.
POST Bulk Card Creation
Path: /api/v1/cards/{id}/bulk_create/
Used to bulk create BIN numbers for cards with the provided ID. The CSV file is a single column and contains the BIN number. For this process, it uses the bulk_create function of BinNumberService.
Response
HTTP 406
Bank Identification Number
The BIN that can be shopped within sales channels are defined. Each BIN is linked to a card. The match is made when the card information is entered in the sales channels. When we enter the details of a card on the Sales Channels>Payment Management>Card Settings page on the Omnitron panel, the bottom of the opened page displays a table with the title Card BIN Numbers.
Potential Responses
GET All BINs
Path: /api/v1/bin_numbers/
Returns all BIN numbers registered on Omnitron.
Filters
Filters can be applied to bin_number_length (6 or 8) in addition to all fields on the serializer. E.g.: ?card=1
Response
GET BIN by ID
Path: /api/v1/bin_numbers/{id}/
Returns BIN numbers with the provided ID.
Response
POST Create BIN
Path: /api/v1/bin_numbers/
It is used to create BIN numbers.
Response / 200
Response / 400
Response / 406
DELETE BIN
Path: /api/v1/bin_numbers/{id}/
Deletes BIN numbers with the provided ID. Returns status 204 in response.
PATCH Create BIN
Path: /api/v1/bin_numbers/{id}/
Updates the bin_number information with the provided ID.
Response
Installment
Used for installments with the cards registered on Omnitron. Covers concepts such as the number of installments and late interest. When we enter the details of a card on the Sales Channels > Payment Management > Card Settings page on the Omnitron panel, the bottom of the opened page displays a table with the title “Term Commission Rates”.
Potential Responses
GET All Installment Instances
Path: /api/v1/installments/
Returns all installment instances.
Filters
Filters can be applied via card, installment_count, interest_rate and is_active. E.g.: ?card=1
Response
GET Installment Detail
Path: /api/v1/installments/{id}/
Returns installments with the provided ID.
Response
PUT-PATCH Update Installment
Path: /api/v1/installments/{id}/
Updates installments with the provided ID.
Response
Response / 400
Response / 406
POST Create Installment
Creates installment objects.
Path: /api/v1/installments
Response / 201
Response / 400
Response / 406
DELETE Installment
Path: /api/v1/installments/{id}
Deletes installments with the provided ID. Returns status 204 in response.
Bank Account
A BankAccount instance must be created for payments by bank transfer. When we enter the details of a bank on the Sales Channels > Payment Management > Banks menu on the Omnitron panel, the opened page displays a table with the title Bank Accounts.
Potential Responses
GET All Bank Accounts
Path: /api/v1/bank_accounts/
Lists all registered bank accounts by sort_order.
Filters
Filtering can be done by ID, bank, IBAN and channel. E.g.: ?channel=1&bank=1
Response
GET Bank Account Detail
Path: /api/v1/bank_accounts/{id}/
Returns bank accounts with the provided ID.
Response
PUT-PATCH Update Bank Account
Updates an existing bank account object with a given body.
Path: /api/v1/bank_accounts/{pk}/
Body
or
Response / 200
Response / 400
Response / 406
POST Create Bank Account
Creates a new bank account object.
Path: `/api/v1/bank_accounts/``
Body
Response / 201
Response / 400
Response / 406
DELETE Bank Account
Path: /api/v1/bank_accounts/{id}/
Updates the is_active field of bank accounts with the provided ID to False. Returns status 204 in response.
Payment Option
Used to create and list payment options for the sales channels on Omnitron. It can be accessed from Sales Channels > Payment Management > Payment Options on the Omnitron panel.
Potential Responses
GET All Payment Options
Path: /api/v1/payment_options/
Returns all payment option objects.
Filters
Filtering can be made via the channel, slug, name, payment_type and is_active fields.
E.x: ?slug=ödeme-seceneği&name=ödemeseceneği
Filters are managed via omnitron.payments.resources.filters.PaymentOptionFilter class.
Response
GET Payment Option Detail
Path: /api/v1/payment_options/{id}/
Returns the payment options with the provided ID.
Response
PUT-PATCH Update Payment Option
Path: /api/v1/payment_options/{id}/
Updates the payment options with the provided ID.
Response
Response / 400
Response / 406
POST Create Payment Option
Used to create new payment option objects. HTTP 400 and HTTP 406 responses may be returned if the request body is not compatible.
Path: /api/v1/payment_options/
Response / 201
Response / 400
Last updated
Was this helpful?

