Prosa

This page provides a guide to integrate Prosa with DEUNA.

Supported operations

Prosa integration in your payment strategy with DEUNA allows you to perform the following operations:

Supported features

• 3DS (Deuna's or external MPI)
• Recurrent Payments
• MSI / MCI
• MOTO

Supported payment methods

• Debit and Credit Cards: Visa and Mastercard.

Integrate Prosa

After searching for Prosa in Connections, you must configure Prosa in your store.

1. Configure Prosa in your store

In Connections, a window like the following will open:

1. Enter the following credentials:

   Credential	Prosa Field	Description	Value in Sandbox
   Moneda		Processor Currency	MXN
   MCC	18 MERCHANT TYPE	Business Line (MCC)	4-digit code. E.g. 3076
   Código de Adquirente	32 ACQUIRING INSTITUTION ID CODE	Acquiring bank code	"127" for BAZ
   Merchant ID	42 CARD ACCEPTOR ID CODE	Code of the institution that accepts the transaction. Suggested to send as "00000000"	Code provided by Prosa
   Receiving Institution Id Code	100 RECEIVING INSTITUTION ID CODE	Applies only to switches. Send the value "000000000"	9-digit code provided by Prosa, if one is not available, place "000000000"
   Pre Authorization hold (days)	126.2 Preauthorization Hold	Days you want the authorization to remain valid. Suggested to keep as "00"	Example: "2"
   ID Terminal	41 CARD ACCEPTOR TERMINAL ID	Terminal ID, assigned by DEUNA (Can be any value, even repeated)	Suggested value: "00000001"
   Afiliación	148.2 Retailer ID	Affiliation code provided by the Merchant's Bank (7 digits for MX)	Example: "8092738"
   Terminal Name	120.2 Terminal Name	Terminal code in Deuna	"DEUNA T1"
   Dueño de la Terminal	60.2 Owner FIID	Bank FIID - B, P or D depending on the bank + 3 digits	"B127" For BAZ
   Red Lógica de la Terminal	60.3 Logic Network	Deuna logic network with Prosa. Constant value "DUNA"	"DUNA"
   Time Offset de la Terminal en Minutos (e.g +1h -> +060)	60.4 Time Offset	Time difference of the terminal with Prosa. Constant value "+000"	Suggested value: "+000"
   Terminal City	43.2 Terminal City	Abbreviation of the City where the business is located (max 4 characters)	Example: "CDMX"
   Terminal State	43.3 Terminal State	State where the business is located (two digits)	Example: "DF"
   Terminal Country	43.4 Terminal Country	Country where the business is located (two digits)	Example: "MX"
   Terminal ZIP Code	POSTAL CODE	Postal code where the business is located (5 digits)	Example: "11510"

2. Choose the type of operation you want to perform:

   • Purchase
   • Authorization

3. Choose if you want to activate 3DS.

4. Click Connect.

2. Process transactions in Prosa

From this point on, you can now process transactions with Prosa through DEUNA.

3. Test your Prosa connection in Sandbox

Credentials

Moneda *
MXN

MCC *
3076

Código de Adquirente *
127

Merchant ID *
123456789

Receiving Institution Id Code *
000000000

Pre Authorization hold (days) *
2

ID Terminal *
00000001

Afiliación *
8092738

Terminal Name *
DEUNA T1

Dueño de la Terminal *
B127

Red Lógica de la Terminal *
DUNA

Time Offset de la Terminal en Minutos (e.g +1h -> +060) *
+000

Terminal City *
CDMX

Terminal State *
DF

Terminal Country *
MX

Terminal ZIP Code *
11510

Simulate approvals and denials

• Approve transactions: order.total_amount <10000 cents
• Deny transactions: order.total_amount > 9999 and < 1000000 cents

"order": {
	"total_amount": 10100, //larger than 9999 cents, then, denied.

Testing Subscriptions and Recurrent Payments

1. Recurrence fields to be included in the purchase v2 request:

   Field name	Type	Values	Comments
   card_id	UUID		Obtained when storing (tokenizing) the card with Deuna's vault: - The card_id is unique for each credit card PAN and Expiration. - A merchant might store the same card_id for different accounts.
   initiator_type	ENUM String (mandatory)	customer, merchant	To define if the transaction is generated by the cardholder or by the merchant
   recurrence.first_time_use	Boolean (mandatory)	true, false	To define if it is the first transaction in the series or a subsequent one
   recurrence.scheduled	Boolean (optional)	true, false	To define if the recurrent payment
   recurrence.id	UUID		Obtained when requesting a first transaction of a recurrent series.
   recurrence.bill_reference	String		Mandatory only in periodic payments requested by the merchant as subscriptions.

2. Prosa subscription and recurrent payment related fields

   Prosa Field	Values	Purchase V2 Input
   Field 22 (POS Entry mode)	01: First Transaction 10: Subsequent transaction	recurrence.first_time_use
   Field 25 (POS Condition Code)	00: Customer-Initiated 01: Merchant-Initiated 08: MOTO	initiator_type market_type
   Field 63 - Token Q2	09: Non-scheduled payment (ecommerce) 02: Automatic scheduled payment 08: MOTO transactions	initiator_type recurrence.scheduled market_type
   Field 63 - Token PJ	First Digit: - E: First Transaction - M: Subsequent Transaction merchant-initiated - C: Customer Subsequent Transation customer-initiated - " ": Customer-Non scheduled Second Digit: - C: Non-Scheduled Payment - R: Scheduled Payment	initiator_type recurrence.first_time_use recurrence.scheduled
   Field 63 - Token C4	Customer-Initiated: "1025100Y3660" Merchant-Initiated: "102410003660" MOTO Transactions: "203310003014" Y*: Antifraud or 3DS Results (0, 1, 2)	initiator_type recurrence.first_time_use market_type
   Field 63 - Token R4	String	recurrence.bill_reference
   Field 63 - Token 17	Network Transaction ID for Visa	Related to recurrence.id, obtained in the first transaction and sent in the subsequents
   ,Field 63 - Token 20	Network Transaction ID for MC	Related to recurrence.id, obtained in the first transaction and sent in the subsequents
   Field 63 - Token CH	Value depending if it is scheduled, and if it was requested by the customer or the merchant	initiator_type recurrence.first_time_use recurrence.scheduled

Postman collection

Credentials Merchant MX.postman_environment.json

Prosa Collections.postman_collection.json