Apple Pay

Introduction

If your payment page is located on the payment gateway side, Apple Pay payments will work without any additional actions from your side because you are automatically registered in Apple with the default domain of the payment gateway.

However, if you want to use your own payment page located on your domain, you must register your domain in Apple and receive all the necessary certificates for your domain before accepting payments via Apple Pay. To do this, follow the steps described in the sections below.

Create Merchant ID

To create your Merchant ID, follow these steps.

1. In the personal area of the Apple Member Center, go to Certificates, Identifiers & Profiles.
2. In the Identifiers section select Merchant IDs.
3. On the resulting page click + (Add) in the right upper corner.
4. In the Merchant ID Description and Identifier fields enter a description of your Apple merchant identifier and the identifier itself accordingly.
   
5. Click Continue.
6. On the resulting page check the data you entered and click Register.
7. On the resulting page click Done.

Certificate registration

To receive payments via Apple Pay, you need to have a key pair (private and public key) and the corresponding public key certificate. The required actions in the Personal Area depend on whether you already have a key pair and the corresponding certificate or not.

Create new certificate

To create a key pair, follow these steps.

1. Log in to your personal cabinet and click in the left panel (Wallet certificates section).
2. Go to Apple Pay tab.
3. Click Create key pair.
   The following form will display.
   
4. Fill in the required fields (see the table below).

• After making the necessary changes click Confirm.

The created key pair will be displayed in the Apple Pay tab (see the figure below).

Proceed to CSR download

Upload previously created certificate

To upload an existing key pair, follow these steps.

1. Log in to your personal cabinet and click in the left panel (Certificates section).
2. Go to Apple Identity tab.
3. Click Add key.
   The following form will be displayed.
   
4. Fill in the following fields.
   • Apple ID - enter your Merchant Apple ID.
   • Password - enter the password for your PKCS12 file.
   • Default domain - enter the domain of your online store.
5. Drag your key pair file to the designated area on the page.
   It will be displayed below.
   
6. Click Create. The uploaded key pair will be displayed in the Apple Identity section.

After uploading your key pair the following actions will become available.

• Edit Apple Merchant ID
• Disable key

Export CSR

To download CSR, follow these steps.

1. Log in to your Personal Area and click in the left panel (Certificates section).
2. Select the required payment service (Apple Pay, Google Pay, or Samsung Pay).
3. Click next to your certificate and select Download key (see the figure below).
   
   Save file dialog will display.
4. Specify the path to which the file will be saved or save it to the default folder.

Also, the following actions are available.

• Edit Apple Merchant ID
• Disable key

Edit Merchant ID

To edit your Apple Merchant ID, follow these steps.

1. Log in to your Personal Area and click in the left panel (Certificates section).
2. Select Apple Pay.
3. Click and select Edit. (see the figure below).
   
   The following form will be displayed.
   
4. Edit Apple ID field and click Confirm.

Disable certificate

To disable a certificate (key), follow these steps.

1. Log in to your Personal Area and click in the left panel (Certificates section).
2. Select the required payment service (Apple Pay, Google Pay, or Samsung Pay).
3. Click next to your certificate and select Disable key (see the figure below).
   
   The following dialog will display.
   
4. Click Confirm.

Whether a disabled certificate is displayed in the personal area depends on Allowed setting that is at the top of the Certificates section (see the figure below).

Setting	Description
Only allowed	Disabled certificates are not displayed in the keys list.
All positions	Disabled certificates are displayed in the keys list. Allowed cell will have No value (see the figure below).

Actions necessary for web integration

For Web integration, follow these steps.

1. Register and confirm your domain in Apple.
2. Create a merchant identification certificate, convert it to a .pem file, and upload it to your server.

This certificate is used to authenticate connections to Apple Pay servers.

Registration of a domain in Apple

To register a certificate in Apple, follow these steps.

1. Log in to your Apple developer account at https://developer.apple.com.
2. Follow Apple developer account help instructions to register a domain.

Select the previously created merchant ID when prompted.

Integration scheme

1. The user in the mobile application selects the payment option using Apple Pay.
2. The payment data is sent to the Apple Pay system for processing.
3. To process the payment data an object PKPaymentToken Object, which has paymentData attribute, is created in the Apple Pay system (here and further see Apple Pay documentation).
4. Apple Pay sends a response to the merchant (mobile application).
5. The merchant exctracts paymentData attribute out of received PKPaymentToken Object object and encodes its contents in Base64.
6. The merchant creates a payment request containing paymentDataattribute, which is received from the Apple Pay response and encoded in Base64, and sends it to the payment gateway for processing (see Request for payment via Apple Pay).
7. The payment system processes the request.
8. The payment system returns a response with the result.
9. The mobile application displays the payment result to the user.

Reference links

Samsung Pay

General information

Before accepting payments via Samsung Pay, follow these steps.

1. Create an account at https://account.samsung.com.
2. Using the created account, register at https://pay.samsung.com/developers.
3. At https://pay.samsung.com/developers create Service and select BPC as your Payment Gateway.
4. Proceed to the actions in the Personal Area of the payment gateway:
   • key pair creation;
   • export of a certificate signing request.

Create key pair

To create a key pair, follow these steps.

1. Log in to your Personal Area and click in the left panel (Certificates section).
2. Go to Samsung Pay tab.
3. Click Create key pair.
   The following form will be displayed.
   
4. Fill in the fields (see the table below).

• After making the necessary changes click Create.

The created key pair will be displayed in the keys list (see the figure below).

Proceed to CSR download.

Export CSR

To download CSR, follow these steps.

1. Log in to your Personal Area and click in the left panel (Certificates section).
2. Select the required payment service (Apple Pay, Google Pay, or Samsung Pay).
3. Click next to your certificate and select Download key (see the figure below).
   
   Save file dialog will display.
4. Specify the path to which the file will be saved or save it to the default folder.

Now you can register your certificate by uploading the CSR to Samsung Pay.

Also, you can disable your certificate.

Complete registration

In your profile at https://pay.samsung.com/developers upload the certificate signing request as Merchant CSR (merchant certificate signing request).

Disable certificate

To disable a certificate (key), follow these steps.

1. Log in to your Personal Area and click in the left panel (Certificates section).
2. Select the required payment service (Apple Pay, Google Pay, or Samsung Pay).
3. Click next to your certificate and select Disable key (see the figure below).
   
   The following dialog will display.
   
4. Click Confirm.

Whether a disabled certificate is displayed in the personal area depends on Allowed setting that is at the top of the Certificates section (see the figure below).

Setting	Description
Only allowed	Disabled certificates are not displayed in the keys list.
All positions	Disabled certificates are displayed in the keys list. Allowed cell will have No value (see the figure below).

Integration schemes

• Integration scheme for payment from a mobile application
• Integration scheme for payment from a web page (payment form on the payment gateway side)
• Integration scheme for payment from a web page (payment form on the merchant's side)

Payment from a mobile application

1. A Customer selects Samsung Pay as a payment method.
2. The application sends payment details to Samsung.
3. Samsung checks the application.
4. Samsung sends a response to the application containing, among other things, the 3ds.data parameter with the encrypted data about the payment.
5. The merchant sends a payment request to the payment gateway. The contents of 3ds.data received from Samsung is included in the paymentToken parameter.
6. The payment gateway decrypts the contents of paymentToken and makes the payment.
7. The payment gateway sends the payment result to the application.
8. The application displays the result to the customer.

Payment from a Web page on the payment gateway side

1. A customer creates an order and starts the payment procedure.
2. The merchant sends an order registration to the payment gateway:
   • One-phase payment;
   • Two-phase payment.
3. The merchant sends a payment request to the payment gateway.
4. The customer selects to pay via Samsung Pay.
5. The payment gateway communicates with Samsung Pay.
6. The customer is redirected to the Samsung Pay page.
7. The customer enters their login.
   
8. The application on the customer's mobile device requests authentication data.
9. The customer is authenticated on their device.
10. The payment gateway exchanges payment data with Samsung Pay.
11. The customer is redirected to the payment result page.

Payment from a Web page on the merchant's side

Payment from a a payment page on the merchant 's side.

1. A customer creates an order on the merchant 's Website.
2. The merchant sends an order registration request to the payment gateway.
   • One-phase payment;
   • Two-phase payment.
3. The payment gateway registers the order and returns the ID of the created.
4. The store redirects the customer to the merchat's payment page.
5. The customer's browser opens the merchant's payment page.
6. The customer gets the payment form.
7. The customer chooses to pay via Samsung Pay Web.
8. The merchant sends a payment request via Samsung Pay to the payment gateway.
9. The payment gateway communicates with Samsung Pay.
10. The payment gateway sends a response to the payment request.
11. The payment form redirects the customer to the Samsung Pay page. For this, the JavaScript scenario that calls the connect function is used. This function must send the data from the response received from the payment request.
    
12. A form for entering the ID is displayed to the customer.
13. The customer enters their ID and confirms the link between their ID and device.
14. Samsung Pay prompts customer authentication.
15. Samsung Pay sends a notification to the customer's device, so they can select a payment card and confirm the payment.
16. The customer confirms the payment.
17. Samsung Pay communicates with the payment gateway.
18. The payment gateway sends the payment result to the payment page.
19. The payment page displays the result to the customer.