Pelcro provides you with various supported payment options and methods that can cater to your different locations, customers, and business needs. This gives your customers the flexibility to selectively use multiple and alternative options for diverse purchases and payment activities, and provides you with a reliable payment system that streamlines a steady revenue stream.
Pelcro provides multiple methods for end-users to make payments online. We've integrated with the best payment gateways to make charging for subscriptions, invoices, e-commerce orders, and more trivial for you. All the payment methods below are available via the platform, API, and user interface libraries.
Pelcro supports all the major card networks listed below by default via our default card forms and fields that are powered by Stripe by default. You can test all payment cards and methods by referring to our Testing documentation.
- Master Card
- American Express
- Discover (USD only)
- Diners Club (USD only)
- JCB (USD only)
Pelcro supports other digital wallets such as Apple Pay and Google Pay. However, additional verification steps are required to use them with Pelcro.
- Apple Pay
- Google Pay
Download this host verification file, and ask your network administrators to upload it in the .well-known directory, which should be publicly accessible and sit at the root directory. Do this for each site that you enabled on Pelcro.
Once done, proceed to your site settings, enable Apple Pay by clicking on the checkbox and saves your changes.
Pelcro also integrates with Apple in-app purchases. It allows you to leverage the Apple store subscriptions.
There are no steps required for you to set up Google Pay, yet the following conditions must be met in order for your end-users to be able to see and use Google Pay as payment option in your UI:
- Google Pay is supported in the end-user's country
- Card is valid and was verified under the end-user's Google account
- The option "Allow sites to check if you have payment methods saved" must be enabled in the browser
- The verified card must be displayed under the "Payment methods" section in payment settings of the browser
- Any browser extension which may prevent Google Pay button from showing may have to be disabled or their settings modified (including but not limited to: Dashlane, uBlock Origin, AdBlock/AdBlock Plus, Privacy Badger, Ghostery)
Here's a sample of the
chrome://settings/payments settings page, displaying a working setup:
Pelcro supports offline payments in the form of cash or check. Processes are implemented across the platform to ensure all the necessary information is collected for an offline transaction. For example, a reference check is required when depositing a check.
- Wire transfer
To view your payments:
- On your Dashboard, hover over your left navigation menu. Choose "Billing" > "Payments".
- You'll be redirected to the payments page, where you can view and manage all your current customer payments.
Once you arrive at the payments page, you will see a detailed list view of all payments to your subscriptions and orders, categorized into six different tabs:
- All: These are all of the payment transactions which have been logged for your customers.
- Succeeded: These are payment transactions which have completed successfully.
- Failed: These are payment transactions which have failed to complete due to insufficient funds, invalid payment source, etc.
- Refunded: These are payment transactions which have been fully refunded back to the customer as a result of cancellation on applicable subscriptions and orders.
- Partially refunded: These are payment transactions which have been partially refunded back to the customer as a result of cancellation on applicable subscriptions and orders, with prorations applied.
- Offline: These are payment transactions made via cash, checks, bank transfers, postal orders, or any other offline means besides online payment methods such as cards, digital wallets, etc.
To help navigate you through your payments, you will also find the following:
- Search button: The search button will allow you to directly find a payment based on a number of options. You may search payments by the customer's name, email address, phone number, company, or department.
- Export button: Allows you to export your payments list, along with all the listed details into CSV format. You can control the range of the payment data to export using the date filters in the top right.
If you want to view more details of a specific payment, either click on the payment amount line item, or alternatively on the ellipsis "···" menu to the right-most column of the desired payment, followed by "View payment".
The payment details page will contain details related to the transaction, including:
- Date: date when the payment transaction was logged on the platform.
- Customer: customer account which the payment transaction originated from.
- Payment Method: payment method which was used to complete the transaction (Card/Digital Wallet/Offline).
- Risk Evaluation: the risk level for each payment to predict whether a payment is likely to be fraudulent.
- Amount: amount which was charged within the payment transaction from customer payment method.
- Currency: currency for the payment transaction and amount.
- Statement descriptor: information that help customers understand their bank/card statements.
- Status: status of the payment transaction (succeeded, failed, etc.)
- Description: information that help customers understand what this payment is tied to on the platform (e.g. subscription creation, subscription cancellation, etc.)
- Receipt URL: a secure, private URL where your customers can view and download PDF copies of the receipt.
You can also view more details of Pelcro components which are related to payments, such as the associated customer with the payment. To do so, click on the three dots "···" menu to the right-most column of the desired payment, followed by "View customer".
- For more information on Customer Details page, please refer to the Customer documentation.
Payments will be generated on Pelcro when users either subscribe to your products and service offerings or buy an eCommerce product. There are a number of ways through which users can make payments:
1. Through the platform:
When your collaborators create subscriptions manually for your users through the platform, you can make a payment directly through the platform. You can select different payment methods, such as Credit card payment, Offline payment, or to directly invoice the customer.
At the Payment section you'll have the options to:
- Automatically charge a payment source on file, under which you'll be able to select one of your stored payment information through your payment gateway from a dropdown.
- Add a new card on file which you can use to pay for the subscription
- Or, invoice the customer directly and receive payment via cash, checks, bank transfers, postal orders, or any other offline means.
2. Through your website:
- Your customers can also make payments directly through your website when they are signing up, subscribing to one of your products or services, or purchasing an eCommerce order during the checkout process.
Payments will be reflected directly on the platform. Using either our default payment modals and components, or even custom ones. Find out more by checking out our React elements which you can plug and play directly.
You can create an offline payment record through your platform for transactions made via cash, checks, bank transfers, postal orders, or any other offline means besides online payment methods such as cards, digital wallets, etc.
- Navigate to the relevant customer details page. Under the payment tab, click the "+" icon.
- Enter the amount, category, currency, and reference details, and click "Enter payment"
- The payment will be reflected on your payments list, as well corresponding payment details page for the customer
- Note that in order for an offline payment to be applied to an invoice, it needs to be entered before the invoice is created and hence before the subscription is created.
- Offline payments can also be entered by navigating to the invoice and marking it as paid - a payment reference will be required and once entered, an offline payment that equals the amount due will automatically be entered into the customer's account.
A dispute (also known as a chargeback, inquiry, or retrieval) occurs when a cardholder questions your payment with their card issuer. An inquiry or retrieval is nothing more than a request for more information about the charge, which may escalate to a chargeback. To process a chargeback, the issuer creates a formal dispute, which immediately reverses the payment. The payment amount (sometimes along with a separate dispute fee), is then deducted from your account balance.
If you would like to keep a record of a disputed payment refund on your refunds list, make sure to select the "Credit Card Chargeback" option when refunding the payment. This maintains a record of the refund on the books, without actually refunding the credit card (In case the refund was issued to the credit card directly through the bank).
If a dispute is raised for a payment, You can mark said payment as disputed by completing the payment transaction with the following card details:
You can directly issue a refund through the platform for charges made to a customer's credit card or their offline payment. For more details, please refer to our refunds section.
When the option for "Payment method expiration notifications" is enabled within billing settings for your site, webhook notifications are triggered to notify customers if any of their payment methods existing on file will expire at the end of the month.
This setting will override Stripe settings for payment expiration notifications.
3D-secure is an extra layer of security required by some card issuers in order to verify a purchase, usually called card authentication. Card authentication gets triggered during the subscription and e-commerce purchase process from the user interface libraries as necessary. Note that 3D secure is currently not triggered when entering a card via the platform, when updating the card from the user interface libraries and for cards requiring continuous off-session authentication for recurring subscriptions.
If authentication is not required, an attempt to make a payment is initiated immediately. If authentication is required, the end-user will be re-directed to the card issuer's website where they will be required to enter a code provided to them to complete the card authentication. Once the code is validated, the end-user will re-directed back to the normal flow and an attempt to collect the payment will be initiated. We provide testing cards for you to simulate this behavior in our testing environments.
The Strong Customer Authentication regulation in Europe requires the use of 3DS for card payments. 3DS is optional in other regions but you can still use it as a tool to reduce fraud.
Our support team is right there for you!
Contact us at [email protected] and we're happy to assist with any questions or concerns.
Updated about 2 months ago