To start receiving payments, you need to create at least one product and then create and assign billing models to it. The billing models reflect the payment types displayed to your customers. There are 4 default billing models each of which can be configured differently to define how the payment is made and to suit your business needs:
– Dynamic Single
– Single + Subscription
In this section we’ll cover the process of creating billing models of different types.
Once the billing model is set up, the QR code and button snippets will be generated, so that it can be placed on your resource to be displayed for the customers. We are explaining this in a respective section.
Creating a New Billing Model
Step 1. Choosing type
On this stage you have to choose the type of billing model:
- Single PullPayment (Example: One-time payment of $5.00) A Single PullPayment accepts one-time payment.
- Dynamic Single PullPayment. Works exactly as a “normal” Single, but the properties (currency, price, name) can be injected straight on your website, not in the Business Console. Suitable for stores with tens/hundreds/thousands items with different descriptions and prices.
- Subscription PullPayment (Example: Monthly subscription of $12.99) Initializes the recurring subscription and has 1 additional option to enable the trial period, so you can charge a fixed amount at a predefined interval.
- Single + Subscription PullPayment (Example: Single payment for 3-day trial and then monthly subscription) Single payment followed by a recurring payment.
Step 2. Name and description. Static billing models
If your selected billing model isn’t dynamic (so the properties are not injected from your website), on step 2 you’ll need to specify these details:
Internal reference name can be like “BM-1” or whatever you find convenient for you. Billing model name and description are self-explanatory.
Step 2. Name and description. Dynamic billing model
If you’d chosen the Dynamic Single PullPayment type on step 1, then you’ll see step 2 a little bit differently:
Here you can choose, which properties are to be specified in the Business Console and which are to be injected from the website. For instance, you can leave the name static and change only description.
Step 3. Payment details. Single PullPayment
If you’d chosen the Single PullPayment billing model type, you’ll have to just specify the price and the local fiat currency you want to display on your website for the convenience of your customers. Once the customer initiates the payment, fiat value will be then converted to PMA according to the current exchange rate.
Step 3. Payment details. Dynamic Single PullPayment
In case of dynamic single the only thing you can do on step 3 is to decide whether the local fiat currency is set in the Business Console or injected from the website dynamically. The price is dynamic by default and that can’t be changed. If you want a static price, you should use the Single PullPayment billing model.
Step 3. Payment details. Subscription PullPayment
In case of Subscription billing model you specify the following details:
– Currency and price – with the same logic as in the Single PullPayment
– Billing Cycle – how often should your customer be billed
– Recurrences – for how long do you wish to bill your customer
– Trial period – the period before the billing starts
Step 3. Payment details. Single+Subscription PullPayment
Here step 3 is quite similar to Subscription. Though you need to set:
– Initial charge – sum the customer needs to pay immediately after subscription. Can be, for instance, less than the subscription payment as a part of the promotion.
– Start subscription billing – period after initial charge after which a regular subscription starts.
Also note that here, you can’t set a trial period.
Step 4. Gas fees
In this step you are informed about how much gas each transaction will cost in Ethers. In-built estimator will show you if you Ether balance is enough to execute the billing model you just set up.
Also, you can switch on the settlement in fiat for the created billing model. Settlement process is described here.
Billing model overview
The overview of a billing model shows the overall details you have defined and the preview, as the customer will see it once he scans the QR code. The QR code is generated and can be embedded either as a snippet or as a button, and then it can be scanned by the customer with the PumaPay Mobile Wallet App.
Each generated billing model will display the gas fee estimations that are expected to be paid once the PullPayment is executed.
Note that while static billing models with details set in the Business Console, are approved by our Compliance team, and only after that you can add the QR code and the buttons. Dynamic billing models don’t need to be approved.
All the details regarding adding the payment instruments to your website are covered in the respective section.
Billing model list
To access all your created billing models you need to first go to the Products section and select a product:
Then you choose the billing model itself, from a list below. Note that you can’t edit created billing models.