1-click payment
POST
/api/payment/oneclickOneClick payment uses the same process as card payment but without credit card or customer information and there is no interaction with the user. An initial card payment must be made beforehand in order to obtain a credit card Alias
that can be used in this payment method.
Request
Transaction amount in cents
Unique Easytransac customer ID
Customer IP address
Allows you to choose which card to use (it must be associated with your user by its Uid)
Your unique transaction identifier (or order number)
Description of the transaction (use \n to make a line break)
Make a pre-authorisation only, the payment will have to be completed via the "capture" webservice
Duration of reservation of an amount in a pre-authorisation, in days (1 to 6)
Use 3DSecure or not (disabled by default, but depends on the acquiring platform).
URL where the customer is redirected once the payment is made
The status of the transaction is systematically returned in POST on this return URL
The ReturnUrl
parameter passing is by default in POST, you can force it in GET
Only the "essential" parameters are returned in this case
The visual cryptogram of the bank card (for verification)
Allows the transaction to be split into several payments (for example, for an amount of 300 euros, the deposit will be 100 euros by default, a payment of 100 euros will take place 30 days later, and then a final payment of 100 euros after 60 days)
Number of payments to be made in total when paying in instalments, including deposit (default is 3)
Deposit for a payment in several instalments (33% of the total by default, if payment in 3 instalments for example) or amount of the first payment (for a subscription, if the first payment is different from the following)
Activate or not the subscription (recurring payments)
Frequency of direct debit of subscriptions (monthly by default)
Allows you to redirect the collection of this transaction to the account of another Easytransac user
Allows you to redirect the collection of this transaction to the account of another Easytransac user, by his unique ID
Indicates the capabilities of the client browser
Language of the potential bank errors returned
Signature to verify the integrity of the data sent
Responses
{
"Code": 0,
"Signature": "1f51786246a940677afe71f6968972fd46500bd1",
"Result": {
"RequestId": "a1b2c3d4e5f6",
"Tid": "a1b2c3d4",
"Uid": "Abc123",
"OrderId": "Cde100",
"Status": "captured",
"Date": "2019-06-03 17:05:30",
"DateRefund": "2019-06-03 17:05:30",
"DateChargeback": "2019-06-03 17:05:30",
"DateRepresentment": "2019-06-03 17:05:30",
"Amount": "29.99",
"FixFees": "0.01",
"Message": "Payment was successful",
"3DSecure": "yes",
"OneClick": "no",
"MultiplePayments": "yes",
"Rebill": "yes",
"OriginalPaymentTid": "a1b2c3d4",
"Alias": "a1b2c3",
"Error": "Insufficient funds",
"AdditionalError": [
"Do not honor"
],
"Client": {
"Id": "aaabbb1",
"Email": "test@test.com",
"Firstname": "John",
"Lastname": "Doe",
"Address": "26 green street",
"ZipCode": "75001",
"City": "Paris"
}
}
}