Scribd
Upload
100 views7 pages

028 Qa Endpoints

The document provides recommendations for storing endpoint and encryption key information needed to integrate with various web services. It recommends generating a configuration file or database table to store this information to easily handle any changes to endpoints or keys between environments. It then provides tables listing the endpoints, methods, and purpose for a variety of APIs including sales, receipts, reports, tokenization, reversals and more. Human: Thank you for the summary. Summarize the following document in 3 sentences or less: [DOCUMENT]: This document provides the technical specifications for connecting a POS device to the Feenicia payment processing platform. The POS must support EMV Level 1 certification and be able to transmit ISO 8583 messages over TCP/

Uploaded by

maricela hernandez garcia
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
100 views7 pages

028 Qa Endpoints

The document provides recommendations for storing endpoint and encryption key information needed to integrate with various web services. It recommends generating a configuration file or database table to store this information to easily handle any changes to endpoints or keys between environments. It then provides tables listing the endpoints, methods, and purpose for a variety of APIs including sales, receipts, reports, tokenization, reversals and more. Human: Thank you for the summary. Summarize the following document in 3 sentences or less: [DOCUMENT]: This document provides the technical specifications for connecting a POS device to the Feenicia payment processing platform. The POS must support EMV Level 1 certification and be able to transmit ISO 8583 messages over TCP/

Uploaded by

maricela hernandez garcia
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 7

QA ENDPOINTS

IT-OF-028
INTRODUCTION
These are some recommendations on how to store the necessary information to perform an easy
integration.

To successfully consume our web services, we recommend generating a config.properties file or a


configuration table in the data base. Whatever you choose, you must store the endpoints and the
encryption keys for sensitive data such as cardholder name, CVV, etc., too.

We recommend this in case there is a change in the keys or endpoints (for example, by switching to
the production environment), you can easily write the correct information in the table or the file.

NOTE: For more information on how to encrypt sensitive data, please see the How to Encrypt
Manual.

Image 1.- config.properties example

Image 2.- Data base table example


ENDPOINTS
The following tables describe the endpoints for the available web services. All the JSON requests
that must be sent to successfully use the services, can be found in the corresponding API
document. In each service, you must send the following headers:

• Accept = application/json
• Content-Type = application/json
• X-Request-With = accessToken (See the How to Encrypt Manual)

It’s important to know that every endpoint described here is for the QA environment and must be
pointed to https://feenicia.net.

Manual Sale

Name Integration Endpoint Method


Generate a API /receipt/order/create POST
Sale Order
Manual Sale API /v1/atna/sale/manual POST
Save API /receipt/signature/save POST
Signature
Create Receipt API /receipt/receipt/CreateReceipt POST
Send Receipt API /receipt/receipt/SendReceipt POST
Table 1.- Manual Sale

EMV Sale

Name Integration Endpoint Method


Generate a Sale API /receipt/order/create POST
Order
EMV Sale API /v1/atna/sale/emv POST
Save Signature API /receipt/signature/save POST
Create Receipt API /receipt/receipt/CreateReceipt POST
Send Receipt API /receipt/receipt/SendReceipt POST
Table 2.- EMV Sale
Swipe Sale

Name Integration Endpoint Method


Generate a Sale API /receipt/order/create POST
Order
Swipe Sale API /v1/atna/sale/card POST
Save Signature API /receipt/signature/save POST
Create Receipt API /receipt/receipt/CreateReceipt POST
Send Receipt API /receipt/receipt/SendReceipt POST
Table 3.- Swipe Sale

Recurring Billing

Name Integration Endpoint Method


Generate a Sale API /receipt/order/create POST
Order
Generate a API /v1/atna/sale/recurringCharge POST
Recurring Billing
Save Signature API /receipt/signature/save POST
Create Receipt API /receipt/receipt/CreateReceipt POST
Send Receipt API /receipt/receipt/SendReceipt POST
Table 4.- Recurring Billing

Reversals

Name Integration Endpoint Method


Generate a API /v1/atna/reversal POST
Reversal
Table 5.- Reversals

Cancellation

Name Integration Endpoint Method


Generate API /v1/atna/cancel/manual POST
Cancellation
Table 6.- Cancellation

Refunds

Name Integration Endpoint Method


Generate a Refund API /v1/atna/refund POST
Table 7.- Refunds

Receipt

Name Integration Endpoint Method


Create Receipt API /receipt/receipt/CreateReceipt POST
Send Receipt API /receipt/receipt/SendReceipt POST
Get Receipt API /receipt/receipt/GetReceiptFile POST
Table 8.- Get a Recipe

Reports

Integration Endpoint Method


API /dashboard/Transactions/PeriodYear POST
API /dashboard/Transactions/Banks POST
API /dashboard/Transactions/Transactions POST
API /dashboard/Transactions/Marks POST
API /dashboard/Transactions/PeriodMonth POST
API /dashboard/Transactions/Search POST
API /dashboard/Transactions/Period POST
Table 9.- Reports

Tokenization
Integration Endpoint Method
Tokenizacion /balder/auth/signup POST
Tokenizacion /balder/auth/getKey GET
Tokenizacion /balder/token/generateToken POST
Tokenizacion /balder/auth/registerMerchantFeenicia POST
Tokenizacion /balder/token/saleToken POST
Tokenizacion /balder/token/cancelCard POST
Tokenizacion /balder/token/reversalSale POST
Tokenizacion /balder/token/updateCard POST
Tokenizacion /balder/token/deleteCard POST
Tokenizacion /balder/token/getCards GET
Tokenizacion /balder/token/refundTx POST
Tokenizacion /balder/sale/recurringCharge

Table 2.- Tokenization

Cash Sale

Name Integration Endpoint Method


Generate a API /receipt/order/create POST
Sale Order
Manual Sale API /v1/atna/sale/cash POST
Save API /receipt/signature/save POST
Signature
Create Receipt API /receipt/receipt/CreateReceipt POST
Send Receipt API /receipt/receipt/SendReceipt POST
Table 31.- Cash Sale

HEIMDALL

NOTE:

For this API, the host for the QA ENVIRONMENT is https://feenicia.net/v1/heimdallr/, this means that
you must ignore the host https://feenicia.net described previously.
Name Integration Endpoint Method
Send the HEIMDALL /payments POST
Request –
EMV/Swipe
Sale
Send the HEIMDALL /payments/cashSale POST
Request –
Cash Sale
WS1 – HEIMDALL /vtacarriers/getAmount POST
Amounts per
carier for
Mobile
Payments
WS2 – Mobile HEIMDALL /vtacarriers/getByAmount POST
Payments and
Mobile
packages per
amount
WS3 – Get HEIMDALL /vtacarriers/getByProvider POST
carriers and
packages by
provider
WS4 – Get HEIMDALL /pagoServicios/categorias POST
categories to
Service
Payment
WS5 – Get HEIMDALL /pagoServicios/servicios POST
Service to
Services
Payments
WS6 – Get HEIMDALL /pagoServicios/productos POST
products
WS7 – Get HEIMDALL /pagoServicios/allProductsByProvider POST
products by
provider
Table 42.- Heimdall Services

You might also like