Yes. Startups can apply even if they do not yet have a long processing history. A new merchant should have a substantially complete website, real inventory, business documentation, ownership information, settlement banking, customer policies and a clear RUO merchant profile ready for review.

Not if you are genuinely new and do not have them. Established merchants should be prepared to provide relevant recent processing history if requested because it can help underwriting understand volume, refunds, disputes and chargeback performance.

Underwriting may review the legal business, ownership/KYC information, settlement banking, website, products, merchant category, inventory/fulfilment, policies, customer-support process and processing history where applicable. Additional information can be requested depending on the merchant.

Timing varies by merchant and by how complete the file is. A clean website, organized documents and fast responses to follow-up questions can prevent avoidable delays, but there is no universal approval time.

No. PeptidePay’s readiness guidance helps merchants prepare, but final eligibility and processing terms are determined through the applicable underwriting process.

Applications are submitted through Boardvia. Every Start Processing Today button on PeptidePay.ca links to the application portal.

The current public tiers are 16.49% for startups/up to $50K monthly volume, 15.00% for $50K–$150K, 12.50% for $150K–$250K and 10.00% for $250K+ monthly volume, subject to underwriting and the applicable processing arrangement.

Potentially. Qualifying established/high-volume merchants may be considered for custom enterprise pricing as low as 6.00% flat. That is not automatic and depends on the merchant’s volume, processing history, disputes, fulfilment, average ticket, business maturity and underwriting.

The pricing page keeps the discussion focused on percentage tiers and merchant fit rather than turning every scenario into a hypothetical dollar-cost calculation. Actual merchant economics depend on approved pricing, volume and the real processing arrangement.

Merchants that grow into a different pricing band or develop stronger processing history can discuss the appropriate pricing path. Any repricing is subject to review and approval rather than being an automatic promise.

Visit the PeptidePay.ca Pricing page for the current public tiers, merchant-readiness information and high-volume pricing path.

RUO means Research Use Only. For payment underwriting, an RUO merchant should present a consistent business profile across the website, product pages, marketing, catalogue, policies and operations. A disclaimer alone does not guarantee approval.

No. The PeptidePay RUO program described on this site is not intended for SARMs. Merchants should disclose their real catalogue during underwriting and remain within the approved merchant profile.

A footer disclaimer does not automatically cure contradictory content. Product and marketing presentation should remain consistent with the merchant profile being presented. Specific eligibility requirements are determined through underwriting and applicable processing/card-network rules.

Product-documentation requirements can vary. Where COAs or testing documentation are applicable to the products being sold, merchants should keep them organized and consistent with the catalogue.

Material catalogue changes should be reviewed before routing those products through the approved processing configuration. Surprise or undisclosed categories can create unnecessary processing problems.

See the RUO Payment Processing Canada page for a deeper merchant-readiness and product-profile walkthrough.

A substantially complete live website is strongly preferred. Underwriting should be able to see the actual products, customer experience, checkout, policies and company information rather than placeholder pages.

PeptidePay strongly prefers merchants to be operational and able to fulfil what they advertise for sale. Inventory, realistic shipping expectations and a workable fulfilment process matter both for underwriting and customer experience.

Merchants should expect to have clear shipping, refund/return, privacy and terms information, along with accessible customer-contact details. Exact requirements can vary by merchant and processor.

Customers who cannot get answers are more likely to dispute transactions with their card issuer. A real support email/contact process and sensible refund handling can prevent avoidable chargebacks.

A mismatch may require clarification or additional documentation. Legal entity, ownership information, website identity and settlement banking should be presented accurately and consistently.

Visit Merchant Requirements & Compliance for the detailed pre-application checklist.

Yes. The WooCommerce path is designed so qualifying merchants can keep WordPress/WooCommerce as the ecommerce layer and connect the payment setup approved for the business.

The intended setup keeps WooCommerce at the centre of product/order administration. Exact order-status behaviour depends on the approved gateway/plugin configuration and should be tested before live traffic.

Yes. An API-oriented path is available for qualifying merchants with custom websites, apps, portals or checkout workflows. Exact documentation depends on the gateway and processing configuration approved for the merchant.

Generally, yes. A custom integration should be implemented and maintained by someone comfortable with secure server-side payment logic, responses, refunds, error handling and testing.

If your business already runs on WooCommerce and does not need custom payment orchestration, WooCommerce may be simpler. API is better suited to custom applications and specialized workflows.

Yes. Technical work does not replace underwriting. The merchant must be approved before live processing is enabled.

See the API Integration page or the WooCommerce page depending on the technical path.

CAD funding is a core part of the Canadian PeptidePay positioning. The exact settlement setup depends on the merchant’s approved processing and banking configuration.

Eligible merchants may have USD funding options depending on approval, banking and processing configuration.

Next-day settlement may be available for eligible approved merchants. Timing depends on underwriting, batch/settlement configuration, bank holidays and applicable banking conditions, so it should not be treated as unconditional.

No. Authorization, capture/batching and bank settlement are different stages. A successful customer payment still follows the approved settlement schedule before proceeds reach the settlement account.

Have the appropriate business settlement account ready and make sure the banking information lines up with the legal entity presented during underwriting.

PeptidePay promotes no-reserve structures for qualifying approved merchant profiles. Any reserve requirement is ultimately determined by underwriting and the applicable processing arrangement, so no-reserve language is not an unconditional guarantee.

A chargeback occurs when a cardholder disputes a transaction through the card-issuing bank and the transaction enters the card-network dispute process. Excessive disputes can create processing risk.

Keep inventory accurate, ship on time, use tracking where appropriate, make charges recognizable, answer customers quickly, publish clear policies and resolve legitimate refund issues before a customer feels forced to call their bank.

No. A merchant-issued refund is generally a voluntary reversal handled through the merchant’s payment workflow. A chargeback is a dispute initiated through the cardholder’s issuer/card-network process.

For established merchants, processing statements and dispute/chargeback history may be reviewed. If something unusual occurred, clear context is better than leaving the reviewer to guess.

Yes. Established merchants can apply and provide relevant processing history. The goal is to review the business and prepare the new approved setup before traffic is intentionally migrated.

Be prepared to provide recent processing statements or other requested history showing sales volume, refunds, chargebacks and relevant account performance.

There is no single automatic threshold. Custom pricing can depend on processing volume, clean history, refund/dispute behaviour, chargebacks, fulfilment, average ticket, business maturity and underwriting.

Generally, a controlled transition is preferable. Merchants should understand the approved new setup, integration and testing before intentionally moving meaningful live traffic.

Be transparent and provide context. Underwriting can evaluate a well-explained past issue more intelligently than an unexplained statement anomaly or undisclosed account history.

See the High-Volume Peptide Payment Processing page for the established-merchant pathway.