CentralPay proposes a full services payment platform that allows you to integrate very easily and smoothly complex payment functionalities thanks to a few lines of code.
CentralPay is a Full Services payment platform covering all the needs of clients, platforms or marketplaces wishing to implement complex payment services integrated into their business offers or processes without having to bear the technical or operational constraints.
Depending on the payment functionalities you want to integrate and your technical knowledge, you either choose between those two methods:
- Integrating a payment page hosted by CentralPay and accessible tnaks to an Iframe : POPIN FORM
- Using the API directly to create your own payment forms : CUSTOM FORM
Doing so, you can access to advanced functionalities and create a customized payment experience corresponding to your usage.
As transactions security is crucial part of the process, CentralPay has developed a unique technology that detects fraudulent transactions without taking the risk of losing your sales.
Our platform is composed of the four following elements:
- An API REST composed of objects delivering payment services
- A portal, back office, allowing a complete management of the overall services
- Entities, "users profiles", owning rights on payment accounts or electronic-money
- A subscription service allowing payment account or e-money creation integrating regulatory controls.
1/ Simple transaction including a Token
As a merchant or a platform, if you are not PCI-DSS compliant Level 1, you are not allowed to stock or use any bank data.
You have then to use a token to charge your transaction by credit card without using any sensible data and having the same agility as a PCI-DSS compliant actor.
NB : the client, your "customer", is the consumer executing a payment.
You receive then a cardTokeId that allows you to initiate a transaction object from your servers without manipulating any credit/debit card number.
Infographic regarding a single payment workflow
NB: you also have the possibility to register, from this transaction stage, a customer that contains the card object including all card data. (please refer to the single payment flow infographic). This step would be useful if want to reiterate a transaction with the same card later on.
2/ Recurring transaction with a Customer
Thanks to the customerID generated (containing the sub-object card with payment data), you can proceed to a new transaction without asking for his/her credit/debit card number to your client once again.
There a several ways of using customerID:
- 1 clic payment, 1 clic upsell, 1 clic cross sell
- Subscription payment
- X multi payment - installment
3/ Direct transaction without Token
This case in not recommended as it necessitates from your side the full load of the secure PCI-DSS process.
Nevertheless if, as a merchant or a platform, you are PCI-DSS level compliant, you can send directly the payment cards to the transaction object without using the "token.js" service. It supposes that no "tokenization process" is done by CentralPay.
You send directly the cards to the API in the transaction object. Those cards are stocked and managed from your side. In that specific case, you do not have to create a customer during a new transaction because you already use the payment data stocked in your PCI-DSS environment.