1. Sales Enablement
  2. Products & Features

SHOPIFY

Shopify is a proprietary e-commerce platform for online stores and retail point-of-sale systems, primarily catering to B2C.

Shopify is an eCommerce platform for businesses to manage online stores. 

Shopify requires adding a % to partner's credit card rates to integrate with their platform. This is not something Paystand does, as we pass along our wholesale credit card rates to our Clients

Paystand will never partner with a vendor who requires additional fees on our credit card rate. Thus, Paystand does not integrate or partner with Shopify. 

Paystand can offer a workaround to redirect payments through Paystand instead of the Shopify checkout, providing Clients with our wholesale credit card rate and other payment options instead of only a 3% fee through Shopify. 

Below you will find the summary of how to control the payment experience in Paystand, using the URL or Embeddable interface, to aid using Paystand alongside your Shopify orders.  

 

Paystand's payment interface ("checkout" or "payment experience") can be set by accepting arguments and attributes from its URL ("$_GET Arguments") or when it is embedded (using Javascript tags).  These settings control virtually every aspect of the payment experience, from the dollar amount the payer will be charged, to whether they can pay partially or otherwise edit the dollar amount, to branding and auto-populating fields, to additional channels in which you want data received.

The comprehensive list of attributes can be found at https://developers.paystand.com/reference#checkout-attributes, with abbreviations for those attributes (handy for long URLs) in the section above, https://developers.paystand.com/reference#checkout-abbreviations.

Some of the attributes are of most importance would be:

  • `paymentAmount`

    • Use this to set the dollar amount, such as the amount owed for an order

  • `fixedAmount`

    • "true" means the payer cannot edit the dollar amount they wish to pay

  • `meta` or a private field

    • To store the order id, customer number, or other information, and in a manner the payer will not see during the payment experience

    • We can surface public fields, if you have additional information you would like to surface to the payer or have them enter in for you (e.g., memo)

  • `payerName`, `payerEmail`, `payerAddressStreet`, etc

    • Use these to auto-populate the name, email, and billing address, and make the experience more convenient for the user

    • They can always edit this information, in case the values you populated are not aligned with their payment instrument of choice

  • `disableFees`

    • This allows you to control whether the Convenience Fees feature is enabled on a payment or not