Solidgate supports accepting wallet payments, including Google Pay and Apple Pay. With these payment methods, customers can easily purchase without manually entering their credit card data during checkout.
Understand how to integrate the payment form into your product. payment form and a Guide
Easily build a safe and simple payment page with our straightforward, step-by-step guide. payment page . The information below is specifically tailored for merchants directly integrating with these digital wallet services.
To start processing Google Pay payments, you must first register with Google. Once the integration is complete, you can add the Google Pay button to your checkout page and start requesting your customer’s encrypted payment information.
How to integrate Google Pay into your payment system:
- Get a Google Merchant ID
Before you can integrate Google Pay, you’ll need to get a Google Merchant ID. You can do this by signing up for a Google Merchant Center account and creating a new merchant profile.
- Add the Google Pay API
To integrate Google Pay into your app, you’ll need to add the Google Pay API to your project. You can find detailed instructions on how to do this in the Google Pay API documentation.
- Add the Google Pay button
Once you’ve added the API, you can add the Google Pay button to your app. This allows users to initiate payments from your app using Google Pay.
- Create a payment request
To create a payment request, you’ll need to provide information about the item being purchased, such as the price and currency. You can also add additional information, such as shipping and billing addresses, to the payment request.
- Process the payment
Once the user has selected Google Pay as their payment method, the API will process the payment and return the payment token to your app.
- Submit the payment token
Use the payment token to submit the transaction to your server-side for further processing, such as charge or authorization. Ensure the data obtained from Google Pay is transferred to the API request for seamless processing.
- Notify the user
Once the transaction has been processed, you can notify the user of the payment status.
For information on integrating with Google Pay, first, refer to the Google Pay API guide, Google Pay Web integration checklist, Google Pay Web Brand Guidelines, Google Pay Android integration checklist, and Google Pay Android brand guidelines.
When you submit a payment data request to the Google API, be sure to include the following parameters:
Once you have completed the integration of Google Pay into your payment system, the next step is to test the integration to ensure that it works correctly.
You can use the Google Pay API Sandbox to test your integration and simulate transactions without incurring any actual charges. You can also use test cards provided by Google to test different scenarios, such as successful and failed transactions.
Google Pay transactions using the
PAN_ONLY data type can be routed for 3D verification steps. This should be done to obtain liability shift and minimize your payment risks. The integration flow is similar to regular card payments and is described below:
Related articles FAQ
Apple Pay be used for in-app purchases on participating apps. Users can add their credit and debit cards to the service, and then use it to make payments. Apple Pay also supports online purchases by allowing users to authenticate purchases with Touch ID, Face ID, or a passcode. It is considered as secure and easy way to make payments using Apple devices.
To integrate Apple Pay into your checkout process, follow these step-by-step instructions:
- Obtain your Apple Pay certificate
Apply for and acquire your own Apple Pay certificate from Apple, which will enable your business to accept Apple Pay payments.
- Create an Apple Merchant ID
Ensure you have an active Apple account, and then create an Apple Merchant ID, which is required to process Apple Pay transactions.
- Integrate Apple Pay
Incorporate Apple Pay into your checkout system, making sure it functions seamlessly with your existing payment process.
- Display the Apple Pay button
Add the Apple Pay button to your checkout page, allowing customers to choose Apple Pay as a payment option.
- Collect and send payment data
After receiving the customer’s payment information through Apple Pay, securely send the data through the API to Solidgate for processing.
- Complete the transaction
Solidgate will handle the transaction and provide confirmation, allowing your business to finalize the sale and deliver the product or service.
Apple Pay Certification
Login to Apple, afterward:
- Click on the Certificates, IDs & Profiles option
- From the newly opened screen select Merchant IDs and click on the (+) button
- Select an ID and enter a short description
- Once the ID is created, a confirmation screen appears
It is recommended that the merchant ensures that the entered data is valid.
- Click the Register button
If the registration is successful a screen showing ‘Registration complete’ appears.
- Click on the row with the newly created ID and choose the Edit button
The options to create Identity and Payment Processing Certificates are shown. On this page, the process of adding/verifying domains can be started.
Creating a Payment Processing Certificate
- From the Edit screen of the Merchant IDs panel choose the “Create Certificate” button
- Answer “No” to the question “Will payments associated with this
Merchant ID be processed exclusively in China?” and click
The next screen contains the instruction on how to create the CSR (and the accompanying it public and private keys).
- Get certificate by signing request (.csr) file from Solidgate Support
This is the file that needs to be uploaded to Apple’s web page.
- From the Browse dialogue choose the file by clicking on the “Choose
File” button and click “Continue”
If the certificate is successfully created, a screen will appear allowing the signed .cer file to be downloaded. Click on the “Download” button and save the file to the disk.
- The Payment Processing Certificate (with a .cer extension) must be sent to Solidgate Support
Creating an Identity Certificate
The identity certificate is needed when merchants want to process Apple Pay payments that originate from within a web page since Apple needs to verify the ownership of the domain from which the payment is initialized. One identity certificate may be used to identify multiple domains.
- From Merchant IDs select the desired ID for creating the identity
Choose the Create Certificate button found in the Merchant Identity Certificate box.
- The steps for creating and exporting the certificates are the same as for Payment Processing Certificates with the only difference being that the following type should be chosen: Key Size – 2048 bits; Algorithm: RSA
Adding Domains to the Apple Merchant ID
To use the “Apple Pay on the Web” each of the domains from which the payment request will be made should be verified. The verification is done by uploading a file on a specified location on the merchant’s website.
Select the Add Domain button from the Merchant IDs screen and the Register Merchant Domain window appears
NOTE: There are a few requirements to the server on which the domain runs (e.g. the merchant server must support the TLS 1.2 protocol and the pages must be served via https). More information can be found here Reference . The above link also contains a complete guide on how to verify the domain.
From the Register, Merchant Domain window enter the desired domain to be verified and should press Continue
Download the file generated by Apple and upload it to the path shown on the screen
Once the file is uploaded the client must click on the Verify button
The uploaded file must be publicly accessible via https.
To process Apple Pay payments, you must configure your Apple developer account, complete the certification process, and enhance your iOS app or website to have the capability to access Apple Pay payments.
For Apple Pay configuration resources, please refer to the following:
Apple Pay transactions using Mastercard and American Express imply a liability shift to the card issuer - similar to 3D secure transactions. Please be aware that although this is a common practice, the issuers are not bound by these terms and can change the liability agreement at any time.
Related articles FAQ