Payment processes

Cash Payment process - SOAP - intermediary PaysafeCard redirection

1. The customer selects the payment method at the business partner checkout page: PaysafeCard or SafetyPay.

2. createDisposition: the business partner makes the SOAP request createDisposition.

   • 2.1. If the result and error code is 0, the business partner redirects the customer to the payment panel.

   • 2.2. If the result or error code is not 0, the business partner shows an error message to the customer:

     Transaction could not be initiated due to connection problems. If the problem persists, please contact our business partner support.

3. Redirection to the payment panel with getCustomerPanel: The customer reaches the PaysafeCard payment panel.

   • 3.1. The customer selects SafetyPay Cash Payment.

   • 3.2. The customer is redirected to the SafetyPay hosted payment page.

4. The customer receives an operation ID code.

   • 4.1. The customer has to go to a Point of Collection to complete the payment.

5. Payment notification delivery: Since the card is assigned to the transaction, transaction status S, PaysafeCard sends a notification to the pn_url.

6. pnUrl handling: Right after the payment notification delivery, the business partner performs the request getSerialNumbers to check the status of the transaction.

   • 6.1. If getSerialNumbers returns the status S, immediately perform the executeDebit request.

   • 6.2. If the response to executeDebit is result and error code 0, the business partner makes a user account top up accordingly or delivers the goods.

---

Online Payment process - SOAP - intermediary PaysafeCard redirection

1. The customer selects the payment method at the business partner checkout page: PaysafeCard or SafetyPay.

2. createDisposition: the business partner makes the SOAP request createDisposition.

   • 2.1. If the result and error code is 0, the business partner redirects the customer to the payment panel.

   • 2.2. If the result or error code is not 0, the business partner shows an error message to the customer:

     Transaction could not be initiated due to connection problems. If the problem persists, please contact our business partner support.

3. Redirection to the payment panel with getCustomerPanel: The customer reaches the PaysafeCard payment panel.

   • 3.1. The customer selects SafetyPay Online Payment.

   • 3.2. The customer is redirected to the SafetyPay hosted payment page.

4. The customer continues with their preferred choice of online payment methods and completes the payment.

5. Payment notification delivery: Since the card is assigned to the transaction, transaction status S, PaysafeCard sends a notification to the pn_url.

6. pnUrl handling: Right after the payment notification delivery, the business partner performs the request getSerialNumbers to check the status of the transaction.

   • 6.1. If getSerialNumbers returns the status S, immediately perform the executeDebit request.

   • 6.2. If the response to executeDebit is result and error code 0, the business partner makes a user account top up accordingly or delivers the goods.

7. okUrl handling: The customer may return to the okUrl. This step is optional.

---

Cash Payment process - SOAP - immediate SafetyPay redirection

1. The customer selects the payment method at the business partner checkout page: PaysafeCard or SafetyPay.

2. createDisposition: the business partner makes the SOAP request createDisposition.

   • 2.1. If the result and error code is 0, the business partner redirects the customer to the payment panel.

   • 2.2. If the result or error code is not 0, the business partner shows an error message to the customer:

     Transaction could not be initiated due to connection problems. If the problem persists, please contact our business partner support.

3. Redirection to the payment panel with getCustomerPanel: The customer reaches the SafetyPay Cash Payment page.

4. The customer receives an operation ID code.

   • 3.1. The customer has to go to a Point of Collection or pay for the operation ID code with one of the available payment options.

5. Payment notification delivery: Since the card is assigned to the transaction, transaction status S, PaysafeCard sends a notification to the pn_url.

6. pnUrl handling: Right after the payment notification delivery, the business partner performs the request getSerialNumbers to check the status of the transaction.

   • 6.1. If getSerialNumbers returns the status S, immediately perform the executeDebit request.

   • 6.2. If the response to executeDebit is result and error code 0, the business partner makes a user account top up accordingly or delivers the goods.

---

Online Payment process - SOAP - immediate SafetyPay redirection

1. The customer selects the payment method at the business partner checkout page: PaysafeCard or SafetyPay.

2. createDisposition: the business partner makes the SOAP request createDisposition.

   • 2.1. If the result and error code is 0, the business partner redirects the customer to the payment panel.

   • 2.2. If the result or error code is not 0, the business partner shows an error message to the customer:

     Transaction could not be initiated due to connection problems. If the problem persists, please contact our business partner support.

3. Redirection to the payment panel with getCustomerPanel: The customer reaches the SafetyPay Online Payment page.

4. The customer continues with their preferred choice of online payment methods and completes the payment.

5. Payment notification delivery: Since the card is assigned to the transaction, transaction status S, PaysafeCard sends a notification to the pn_url.

6. pnUrl handling: Right after the payment notification delivery, the business partner performs the request getSerialNumbers to check the status of the transaction.

   • 6.1. If getSerialNumbers returns the status S, immediately perform the executeDebit request.

   • 6.2. If the response to executeDebit is result and error code 0, the business partner makes a user account top up accordingly or delivers the goods.

7. okUrl handling: The customer may return to the okUrl. This step is optional.