Billing - Overview

The billing system is how you're able to bill customers. The goal of the billing system is to make it easy for companies to have professional level billing that is flexible and extendable.

Setup

1. Add target entity alias

doctrine:
  // ...
    orm:
      resolve_target_entities:
        Parthenon\Billing\Entity\CustomerInterface: App\Entity\Team

2. Add Routes

parthenon_billing_controllers:
    prefix: /api
    resource: ../../src/Parthenon/Billing/Controller/
    type: annotation

Main Configs

Name	Type	Description
enabled	boolean	If billing is enabled
customer_type	string	team if teams are enabled and the team owner should be billed. Or user if single accounts are being used.
plan_management	string	config if static plans from the Parthenon yaml config should be used. Or athena if they are to be managed in Athena.
payments	array	The payments config

Payment Configs

Name	Type	Description
provider	string	What payment provider is to use.
pci_mode	boolean	If PCI mode is enabled where it's possible to sent card details directly to the payment gateway.
return_url	string	The return url to give to the payment gateway
cancel_url	string	The cancel url to give to the payment gateway
adyen	array	The adyen config
stripe	array	The Stripe Config

Adyen Configs

Name	Type	Description
api_key	string	The API key
merchant_account	string	The merchant account for Adyen.
test_mode	boolean	If you're using test servers for Adyen. For development mode.
prefix	string	The prefix Adyen has given you for production access.

Stripe Configs

Name	Type	Description
private_api_key	string	The private API key
public_api_key	string	The public API key
payment_methods	array	The payment methods to be used for Stripe hosted checkout

PCI Mode

Processing card details yourself is a security risk and some payment providers demand you've passed PCI checks to even allow it.