Core Business Process Description

Deposit process

The merchant calls POST /api/pay/unifiedOrder to create a deposit order.

TarsPay returns payUrl and payData; the merchant should direct the payer to it as is.

After the payer completes the payment, TarsPay sends an order status callback to the notifyUrl in the order request.

The merchant verifies the signature, reconciles the order, completes idempotent processing and returns plain text OK.

If no callback is received or a compensating check is needed, call POST /api/payInInfo to query the order.

The currency is fixed to ARS.

amount must be a multiple of 100.

See the Attachment Code Table for the available wayCode values.

returnUrl is only used for front-end redirection and cannot replace the asynchronous notification.

The merchant calls POST /api/payOut/unifiedOrder to create a withdraw order.

wayCode supports CVU or CBU; see the Attachment Code Table for the values.

code = 0 only means the order has been accepted or queued.

The merchant obtains the final result through the order status callback or POST /api/payOutInfo.

The currency is fixed to ARS.

amount only supports positive integers; decimal points are not supported.

customerAccountNumber must be a 22-digit CVU or CBU.

The final status is based on the state returned by the callback or the order query.

Read the raw JSON request body and the X-RESP-SIGNATURE header.

Verify the callback signature with the signature scheme configured for the merchant.

Check mchNo, the order numbers, the currency and the amount.

Process idempotently by order number and order status.

Execute the full success business logic only when state = 2; handle other states according to the Attachment Code Table.

Return plain text OK after processing.

The same order may receive duplicate notifications. Never ship goods, credit or refund repeatedly because of callback retries.