A transaction represents an accepted, refused or discontinued payment request, an application for authorization, reimbursement or credit or cancellation.
The transaction object allows to debit your customer from his payment method, usually a credit card, using the cardTokenId that has just been created or from a Customer object if it has been previously registered.
During a transaction with a cardTokenID, a Card object is returned as a cardId.
The transaction has a "success" status when an application for authorization has been issued by the bank. The bank return code is = 0.
Transaction Success can be Capture. If Capture is not done, the card is not debited. You have 7 calendar days to capture a Transaction Success
This status indicates that a transaction encountered a blacklisted element. It can be an IP, a phone number, an email address, or a card number.
If you "capture" a transaction success, Centralpay wil send charge the card and send the operation to CLEARING
The transaction has a "failure" status when the authorization has not been issued by the Bank issuing the card. You will receive in addition the code (Bank Code < 100)
See the return codes
This status is the cancellation of a capture request before it is cleared. It is possible to cancel a transaction between the transaction status success and cleared.
The 3D authentification has failed. The card holder has submitted an incorrect code.
This status indicates that a transaction has been been debited on your customer's card. At this step, you can't Cancell it but you can still REFUND it.
The transaction has been refused because it encountered an element of an acceptance rule.
During the first payment, a CardTokenID is used to create a transaction.
A one-off payment (single transaction) is a transaction during which a debit/credit card is used for a single payment.
Once this step is completed, a Customer object can be created so that it can be used again in case of recurring payments.
There are two ways to manage payment cards during a one-off payment:
To process recurring payments or transactions (1-click, subscription, installment...), you have to create first a Customer object in which one or more cards can be associated. This is processed as a result of a successful first transaction.
For more information, please refer to the "customer" object
A chargeback (also known as unpaid) occurs when a customer (cardholder) contests a transaction with the bank. The issuing Bank of the card then addresses a dispute to the acquiring bank so that it proceed to the payment immediately.
For any credit card payment, your customer has the possibility to contest a payment for up to 13 months. In France, an opposition is allowed only in case of a fraudulent card utilization. However, in other European countries, the bank card can be used as part of a commercial dispute.
Object:
A request for information is sent to you by your client in order to obtain information on the nature of the carried out operation. At this stage, it is not considered as an unpaid transaction, however it should evolve according to the answers made.
Action:
To respond by providing the nature of the service issued, proof of customer's consent and/or proof of delivery.
Object:
Notifies that the information request is closed. The provided information will prevent the unpaid.
Action:
No action to carry out
Object:
An unpaid is addressed to you by your client. The transaction amount will be debited from your account in order to allow the refund. A non-refundable processing fee applies for the processing of the dispute.
Action:
You have a 3-week deadline to respond by providing proof of consent of the transaction and/or proof of delivery.
Object:
The unpaid was rejected. The funds will be reimbursed to you.
Action:
No action to carry out
Object:
The unpaid is retained. The funds will not be reimbursed you.
Action:
No action to carry out
Object:
The funds lost during the chargeback will be reimbursed to you.
Action:
No action to carry out
There is a dispute solution process that consists in contesting, in some cases, the unpaid and to prove that the payment is valid.
When a dispute occurs, a notification mentionning the disputed payment is sent to CentralPay. CentralPay will send you as well a notification. An dispute object is created with a status that requires a response. If during your integration you have set up hooks you will also be informed by an event.
You are able to view the status of each of the disputes through the platform, to read the reasons the client has deferred to the card provider, and to deal with the dispute by contesting it either by submitting a relevant "proof" or by accepting it.
When a transaction has been successfully completed, Centralpay can send a payment confirmation email to the address that is fulfilled in the receiptEmail parameters of the transaction request.
This payment confirmation has a formatted layout displaying the different payment information, however you can configure several settings from the Back-Office at your convenience.
Please check below an example of a payment confirmation email:
List of the elements marked with arrows:
Point of sale information:
The elements 1, 2, 3, 4 highlighted are set up in the "Point of sale" prameters of your account:
Bottom content of the receipt:
Note: a Merchant Admin profile is requirred to proceed to thoses set ups.
You can now go to the Receipt Email edition page and enter the following parameters:
The content of the Footer (field number 5) will be displayed at the end of the email.
This template will be used only for the selected point(s) of sale.
The language depends on the parameters of the browserUserAgent, browserAcceptLanguage and enduserLanguage sent in your transaction request.
The Payment Confirmation Language:
If you want the card holder to receive the payment confirmation in a specific language, you must fill in the endUserLanguage value.
Otherwise, the value filled in the browserAcceptLanguage field is used and English by default if nothing is completed.
| endUserLanguage string (2) |
User language (browser default) Required: NO Validation: [a-z]{2} Alpha2 ISO 639-1 language code Note: Payment Receipt language will be defined by endUserLanguage. |
| browserAcceptLanguage string (255) |
List of languages installed in the browser Required: NO Validation: [a-z]{2}([-A-Z]{2})? Alpha2 ISO 639-1 language code and, optional, Alpha2 ISO 3166-2 country code (optional) Examples: de, en-US, en-GB | fr, es-ES, it | es, en-GB, nl, ru |
| browserUserAgent string (255) |
Browser and operating system identifier Required: NO Validation: .{0,255} Example: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.186 Safari/537.36 |
