03.01 Merchant Creates Deposit

Status: draft for discussion

1. Goal

Merchant must be able to create a deposit in the new system and receive a Hosted Payment Page link.

A deposit can be created by:

• merchant through integration;
• platform user through Back Office for testing;
• merchant user through Back Office for testing, if their role allows it.

2. Scenario

1. Merchant selects a brand and a payment method inside that brand.
2. Merchant sends transaction and customer data.
3. The system checks whether there is enough data to start.
4. If required data is missing, the transaction is not created.
5. If there is enough data, the system creates the transaction.
6. Merchant receives Hosted Payment URL and transaction identifier.
7. Customer opens Hosted Payment Page.
8. The system performs routing and provider execution.
9. Merchant receives updates through webhooks.

3. Required Data

Merchant must send:

• transaction reference;
• brand;
• payment method inside that brand;
• amount and currency;
• customer details, where email is required;
• redirect URLs;
• webhook URLs.

Exact field names and validation rules are proposed by the development team.

4. Duplicate Transaction

If merchant tries to create a transaction with an already existing reference, the system must not create a duplicate.

5. What Customer Sees

Customer does not see routing, providers, or technical statuses.

Customer opens Hosted Payment Page and goes through a clear payment flow.