Integration Scenarios

BLIK Payment with Redirection

Payment with Redirection to the BLIK Payment Page

1. The buyer selects the BLIK payment method.
2. The shop authenticates with PayU by retrieving an OAuth token.
3. The shop creates the order by sending an order with the OAuth token received from PayU.
4. PayU registers the transaction with BLIK and returns a response to the shop with the ID of the created order.
5. The shop directs the buyer to the BLIK payment page via an intermediary page where mandatory information about PayU acting as the personal data controller during the payment process is presented.
6. The buyer enters a BLIK authorization code.
7. BLIK sends a notification to the mobile application of the buyer's bank, from which the BLIK authorization code was generated, that the payment must be authorized.
8. The buyer authorizes the payment in the bank's mobile application.
9. The buyer is notified of the transaction status and is redirected to the shop page.

Payment with Redirection to the PayU Payment Page

1. The buyer selects payment via PayU.
2. The shop authenticates with PayU by retrieving an OAuth token.
3. The shop creates the order by sending an order with the OAuth token received from PayU.
4. PayU returns a response to the shop with the redirectUri and the ID of the created order.
5. The shop redirects the buyer to the PayU payment page.
6. The buyer selects the BLIK payment method.
7. The buyer enters a BLIK authorization code.
8. BLIK sends a notification to the mobile application of the buyer's bank, from which the BLIK authorization code was generated, that the payment must be authorized.
9. The buyer authorizes the payment in the bank's mobile application.
10. The buyer is notified of the transaction status and is redirected to the shop page.

Payment with a BLIK Authorization Code

When placing an order, the buyer can enter a BLIK authorization code on the shop's website. The shop should handle the following basic scenarios:

Placing an Order for the White Label Payment with BLIK Authorization Code

1. The shop presents a field for entering the BLIK authorization code.
2. The buyer generates a BLIK authorization code in the bank's mobile application, and enters it on the shop's website.
3. The shop authenticates with PayU by retrieving an OAuth token.
4. The shop creates the order by sending an order with the OAuth token received from PayU.
5. PayU registers the transaction with BLIK and returns a response to the shop with the ID of the created order.
6. The shop displays relevant information to the buyer.
7. BLIK sends a notification to the mobile application of the buyer's bank, from which the BLIK authorization code was generated, that the payment must be authorized.
8. The buyer authorizes the payment in the bank's mobile application.
9. The shop receives a notification that the payment has been authorized.

Unsuccessful Order Request for White Label Payment with BLIK Authorization Code – Invalid BLIK Code

1. The shop presents a field for entering the BLIK authorization code.
2. The buyer generates a BLIK authorization code in the bank's mobile application, and enters it on the shop's website.
3. The shop authenticates with PayU by retrieving an OAuth token.
4. The shop creates the order by sending an order with the OAuth token received from PayU.
5. PayU registers the transaction with BLIK and receives information about an invalid BLIK code.
6. PayU returns a response with the appropriate error code and the ID of the created order.
7. The shop displays an error message to the buyer.

UID Token Payments

Before presenting the available payment methods, the shop retrieves them and checks whether the buyer has a UID token.

If the buyer has a UID token, the shop presents UID token payment as the default BLIK option. The shop must also let the buyer enter a BLIK authorization code – the service requires this option.

The UID token enables payment authorization by associating the buyer's bank mobile application with the token. When the buyer selects UID token payment, BLIK sends a notification to the mobile application associated with the token, where the buyer authorizes the payment. If the buyer cannot confirm the payment in the mobile application originally linked to the UID token, they can enter a BLIK authorization code instead and continue the payment.

If the buyer enters a BLIK authorization code generated in a different bank's mobile application than the one linked to the token, that application is also linked to the token. The list of bank mobile applications associated with the buyer's UID token is returned when payment methods are retrieved. If the UID token is linked to more than one bank mobile application, the shop must show a list of these applications, so that the buyer knows in which application to authorize the payment.

Note that...

In the previous version of this process, the shop learned that more than one bank mobile application was assigned to the UID token from an error response (OrderCreateResponse). This response contained the complete list of the bank mobile applications associated with the UID token. To complete the order, the shop sent a new order with the bank mobile application chosen by the buyer.

The UID token registration requires the buyer to save it at the payment authorization stage in the bank's mobile application. Token registration always takes place in the context of a BLIK code authorization, so the token is associated with the bank's mobile application in which the BLIK code was generated.

Possible Number of Registered Applications

One BLIK token can be associated with up to 5 bank mobile applications.

The UID token is deregistered at the buyer's request in the bank's mobile application. The token is deleted once all its links with bank mobile applications are removed.

With the UID token, the buyer can pay without confirming the payment in the bank's mobile application. For details, contact your PayU account manager.

Placing an Order for White Label Payment with a BLIK Authorization Code and the UID Token Registration

1. The shop authenticates with PayU in the context of the buyer by retrieving an OAuth token.
2. The shop uses the returned OAuth token to send a new request for retrieving payment methods.
3. PayU does not return the UID token.
4. The shop presents payment with a BLIK authorization code as the default BLIK payment option.
5. The buyer pays for the order by entering a BLIK authorization code from the bank's mobile application.
6. The shop creates the order by sending an order with the OAuth token received from PayU.
7. PayU registers the transaction with BLIK, along with the request to create the UID token, and returns a response to the shop with the ID of the created order.
8. The shop displays relevant information to the buyer.
9. BLIK sends a payment authorization notification to the bank mobile application which has been associated with the UID token during its registration.
10. The buyer authorizes the payment in the bank's mobile application and saves the UID token.
11. The shop receives a payment authorization notification.
12. PayU receives information from BLIK that the buyer has saved the UID token.
13. PayU activates the UID token for the buyer.

Placing an Order for the White Label Payment with the UID Token

1. The shop authenticates with PayU in the context of the buyer by retrieving an OAuth token.
2. The shop uses the returned OAuth token to send a new request for retrieving payment methods.
3. PayU returns the UID token, associated with a single bank's mobile application.
4. The shop presents the UID token payment as the default service within the BLIK payment method.
5. The buyer pays for the order by selecting the UID token payment.
6. The shop creates the order by sending an order with the OAuth token received from PayU.
7. PayU registers the transaction with BLIK and returns a response to the shop with the ID of the created order.
8. The shop displays relevant information to the buyer.
9. BLIK sends a notification about required payment authorization to the bank's mobile application which was associated with the UID token during its registration.
10. The buyer authorizes the payment in the bank's mobile application.
11. The shop receives a payment authorization notification.

Placing an Order for the White Label Payment with the UID Token, without the Buyer's Confirmation

1. The shop authenticates with PayU in the context of the buyer by retrieving an OAuth token.
2. The shop uses the returned OAuth token to send a new request for retrieving payment methods.
3. PayU returns the UID token, associated with a single bank's mobile application.
4. The shop presents the UID token payment as the default service within BLIK.
5. The buyer pays for the order by selecting the UID token payment.
6. The shop creates the order by sending an order with the OAuth token received from PayU.
7. PayU registers the transaction with BLIK and returns a response to the shop with the ID of the created order.
8. The shop displays relevant information to the buyer.
9. The shop receives a payment authorization notification.

Placing an Order for the White Label Payment with a BLIK Authorization Code, and the UID Token Registration for the Buyer Who Already Has a Token

1. The shop authenticates with PayU in the context of the buyer by retrieving an OAuth token.
2. The shop uses the returned OAuth token to send a new request for retrieving payment methods.
3. PayU returns the UID token, associated with a single bank's mobile application.
4. The shop presents the UID token payment as the default service within BLIK.
5. The buyer chooses authorization with a BLIK authorization code from the bank's mobile application.
6. The shop creates the order by sending an order with the OAuth token received from PayU.
7. PayU registers the transaction with BLIK along with a request to link another bank's mobile application and returns a response to the shop with the ID of the created order.
8. The shop displays relevant information to the buyer.
9. BLIK sends a request to save the UID token to the bank's mobile application where the BLIK code was generated, along with a notification to authorize the payment.
10. The buyer authorizes the payment in the bank's mobile application and saves the UID token.
11. The shop receives a payment authorization notification.
12. PayU receives information from BLIK about the assignment of the UID token to another bank's mobile application.

Placing an Order for the White Label Payment with Multiple Bank Mobile Applications Associated with the UID Token

1. The shop authenticates with PayU in the context of the buyer by retrieving an OAuth token.
2. The shop uses the returned OAuth token to send a new request for retrieving payment methods.
3. PayU returns the UID token with a list of the associated bank mobile applications.
4. The shop presents the UID token payment as the default service within BLIK, along with a list of the associated bank mobile applications.
5. The buyer pays for the order by selecting the UID token payment for a specific bank's mobile application.
6. The shop creates the order by sending an order with the OAuth token received from PayU.
7. PayU registers the transaction with BLIK and returns a response to the shop with the ID of the created order.
8. The shop displays relevant information to the buyer.
9. BLIK sends a notification about required payment authorization to the bank's mobile application chosen by the buyer.
10. The buyer authorizes the payment in the bank's mobile application.
11. The shop receives a payment authorization notification.

Placing an Order for the White Label Payment with the UID Token, when the Token Is Associated with Multiple Bank Mobile Applications – Previous Process Version (Ambiguity)

1. The shop authenticates with PayU in the context of the buyer by retrieving an OAuth token.
2. The shop uses the returned OAuth token to send a new request for retrieving payment methods.
3. PayU returns the UID token without the associated bank mobile applications.
4. The shop presents the UID token payment as the default service within BLIK.
5. The buyer pays for the order by selecting the UID token payment.
6. The shop creates the order by sending an order with the OAuth token received from PayU.
7. PayU registers the transaction with BLIK and receives an ambiguity error – the request does not specify to which bank's mobile application the authorization notification should be sent.
8. PayU returns a response with the corresponding error code and a list of bank mobile applications assigned to the token.
9. The shop displays a list of available bank mobile applications to the buyer.
10. The buyer chooses the bank's mobile application.
11. The shop creates a new order by sending an order with information about the selected bank's mobile application.
12. PayU registers the transaction with BLIK and returns a response to the shop with the ID of the created order.
13. The shop displays relevant information to the buyer.
14. BLIK sends a notification about required payment authorization to the bank's mobile application chosen by the buyer.
15. The buyer authorizes the payment in the bank's mobile application.
16. The shop receives a payment authorization notification.