3.28. /api/v4/create-recurring-payment
Introduction
Create recurring payment is initiated through HTTPS POST request by using URLs and the parameters specified below. Use OAuth RSA-SHA256 for authentication.
API URLs
Integration |
Production |
---|---|
https://sandbox.payneteasy.com/paynet/api/v4/create-recurring-payment/ENDPOINTID |
https://gate.payneteasy.com/paynet/api/v4/create-recurring-payment/ENDPOINTID |
Request Parameters
Note
Parameter Name |
Description |
Value |
---|---|---|
rp_card_type |
SRC - source card. DST - destination card. |
Necessity : RequiredType : noneLength : none |
client-orderid |
Connecting Party order ID. Supported for SRC and DST type. |
Necessity : RequiredType : StringLength : 128 |
Merchant login |
Connecting Party’s login name. Supported for SRC and DST type. |
Necessity : RequiredType : StringLength : 20 |
Endpoint |
Endpoint ID. Supported for SRC and DST type. |
Necessity : RequiredType : NumericLength : 10 |
order_desc |
Description of Recurring payment. Supported for SRC and DST type. |
Necessity : RequiredType : NumericLength : 65K |
credit-card-number |
Payer`s credit card number. Supported for SRC and DST type. |
Necessity : RequiredType : NumericLength : 20 |
currency |
Currency type. Supported for SRC and DST type. |
Necessity : RequiredType : StringLength : 3 |
country |
Payer`s country. Not supported for DST. |
Necessity : RequiredType : StringLength : 2 |
city |
Payer`s city. Not supported for DST. |
Necessity : RequiredType : StringLength : 128 |
zip-code |
Payer`s zip-code. Not supported for DST. |
Necessity : RequiredType : StringLength : 10 |
address1 |
Payer`s address. Not supported for DST. |
Necessity : RequiredType : StringLength : 256 |
first-name |
Payer`s first-name. Not supported for DST. |
Necessity : RequiredType : StringLength : 128 |
last-name |
Payer`s last-name. Not supported for DST. |
Necessity : RequiredType : StringLength : 128 |
customer-ip |
Payer`s IP address. Supported for SRC and DST type. |
Necessity : RequiredType : StringLength : 45 |
Payer`s email. Not supported for DST. |
Necessity : RequiredType : StringLength : 128 |
|
card-printed-name |
Payer`s card printed name. Required for SRC, optional for DST. |
Necessity : Required/OptionalType : StringLength : 128 |
expire-year |
Payer`s card expire year. Required for SRC, optional for DST. |
Necessity : Required/OptionalType : NumericLength : 4 |
expire-month |
Payer`s card expire month. Required for SRC, optional for DST. |
Necessity : Required/OptionalType : NumericLength : 2 |
ssn |
Social security number field. Not supported for DST. |
Necessity : OptionalType : StringLength : 32 |
cvv2 |
Payer’s CVV2 code. CVV2 (Card Verification Value) is a three- or four-digit number printed on the back of the card in the signature area. |
Necessity : OptionalType : NumericLength : 3-4 |
birthday |
Payer`s birthday date. Not supported for DST. |
Necessity : OptionalType : 8/Numeric, YYYYMMDDLength : 8 |
phone |
Payer`s phone number. Not supported for DST. |
Necessity : OptionalType : StringLength : 128 |
state |
Payer`s state. Not supported for DST. |
Necessity : OptionalType : StringLength : 2-3 |
period |
Period can be day, week and month. In case if daily is chosen, client will be charged every day. If week - every 7 days. If monthly is chosen, client will be charged on the same date of the month, from the starting date, no matter how many days there are in a month. Not supported for DST. |
Necessity : OptionalType : StringLength : 32 |
interval |
Interval is a multiplier applied to the period. For example, if interval of 2 and period ‘Daily’ is selected, client will be charged once every 2 days. Not supported for DST. |
Necessity : OptionalType : intLength : - |
start-date |
Date, when first charge is scheduled. If start date is set as a current date and type is set as auto, first charge will be made today. Supported for SRC and DST type. |
Necessity : OptionalType : 8/Numeric, YYYYMMDDLength : 8 |
finish-date |
Date, when the Payer will be charged last time. Supported for SRC and DST type. |
Necessity : OptionalType : 8/Numeric, YYYYMMDDLength : 8 |
max-repeats-number |
Index of recurring transaction, first charge will hold the index of 0. Current repeats number increases even if a charge was unsuccessful. When current repeats number reaches max repeats number, Recurring payment goes into stop status and client is charged no more. If a charge was made automatically, no additional charges will be made(unless done manually), even if a recurring payment is stopped and rescheduled again. Supported for SRC and DST type. |
Necessity : OptionalType : intLength : - |
amount |
Amount of currency must be the same as currency on the project assigned. Upon reaching finish date, Recurring payment will go into stop status. Supported for SRC and DST type. Necessity becomes required if amount-from and amount-to or amount-sequence are not used. |
Necessity : OptionalType : StringLength : 255 |
amount-from |
If amount from+amount to is chosen, every charge will be of random amount between these two numbers. Supported for SRC and DST type. Necessity becomes required if amount and amount-sequence are not used. |
Necessity : OptionalType : StringLength : 255 |
amount-to |
If amount from+amount to is chosen, every charge will be of random amount between these two numbers. Supported for SRC and DST type. Necessity becomes required if amount and amount-sequence are not used. |
Necessity : OptionalType : StringLength : 255 |
amount-sequence |
If amount sequence is chosen, client will be charged amounts from this list. Example of setting up amount sequence: 10.5, 24.6, 32.0. If repeats number is higher than amount sequence number of elements, every new charge will be with last amount in amount sequence. In order for charges to begin from the first amount in the chain, current repeats number must be set as 0. Supported for SRC and DST type. Necessity becomes required if amount-from and amount-to or amount are not used. |
Necessity : OptionalType : StringLength : 255 |
purpose |
Purpose of transaction. Not supported for DST. |
Necessity : OptionalType : StringLength : 128 |
notify_url |
Notify url field. server_callback_url parameter can also be used. For more information please see Connecting Party Callbacks. Supported for SRC and DST type. |
Necessity : OptionalType : StringLength : 1024 |
server_callback_url |
URL, where the transaction status is sent to. Connecting Party may use server callback URL for custom processing of the transaction completion, e.g. to collect payment data in the Connecting Party’s information system. For the list of parameters which come along with server callback to server_callback_url refer to Connecting Party callback parameters. |
Necessity : OptionalType : StringLength : 128 |
Response Parameters
Note
Response Parameters |
Description |
---|---|
type |
The type of response. Example: create-recurring-payment-response. |
recurring-payment-id |
Recurring ID assigned to the order by Payneteasy. |
status |
See Status List for details. |
serial-number |
Unique number assigned by Payneteasy server to particular request from the Connecting Party. |
Request Example
POST /paynet/api/v4/create-recurring-payment/ HTTP/1.1
User-Agent: curl/8.4.0
Accept: */*
Authorization: OAuth oauth_consumer_key="ErwinTestMerchant", oauth_nonce="qdyD66xc8sDEQwo3r12VjJfJhAOXuj6O", oauth_signature="eZve%2FSvPCTBXtQM%2BEwTEROtsQE27gZJr36EThL8ECCrnWH9Xw8JxcysNEPTG5HfcYwR2IOjDk3uiSNFa1oT2bQT9XONQTl1JVTOhIiMrMJT7GT1rGuLSsEvghaBoRLrcth6SC0c%2F%2FINyOxmIc%2B79E3T8hkpH6J6VI%2BSRG162%2BlHBPc1u1SGGnhkkRYU621AUGu2FDrc4neob4QJSm%2BaF3a0AgWDGiLbeQ0Ivn3YJ441EKd99kBWdaCuUp0eSfcmh3U2Js66edCjWXDEW7uuywP%2BU%2FBEeq06XxoVNGE2NF2LArXgoNqfzz2Tpisq35%2FE7Yg%2F9hphww75HMoJCECe0yVIHmKXd8HBDNMyT7gg3w5bnKbo%2FURX0m%2Fpe7bxkJ1mLNsKouHVkvjLZKpWVVUyCl%2BJ3x0BoEN5QK7xh0fNbV4Ue9TUOz59q0v%2B7lz5E1B4TvxQ9pa%2FmNCl4P2JgTosLvXNcdGn9Dq0TC0gb62O2W81MoZAljJQew%2FcKAUFTXBMZK6eIXzA81BPQVejv8nIVsvHKNo2Ko0s3hJPKGaeVAN0gyUAPw0%2BsJI3bnN2CPSW92xysGRWJYBtsHhqDhmgtoDNvw7LFB6BzRk5GPa9iQju34l47GsCUUIs3%2ByipIl7Q3HnM%2Bet9L8JSl7K02MwR6zlLxtd9UXHDq3pnmKzly6I%3D", oauth_signature_method="RSA-SHA256", oauth_timestamp="1721312072", oauth_version="1.0"
Content-Length: 595
Content-Type: application/x-www-form-urlencoded
Connection: keep-alive
address1=1234%20Peace%20street
&amount=55
&birthday=1980-01-02
&card-printed-name=JOHN%20SMITH
&city=Chicago
&client-orderid=1575634981130
&country=US
&credit-card-number=4464920026265488
¤cy=USD
&customer-ip=1.2.3.4
&cvv2=123
&email=john.smith%40example.com
&expire-month=12
&expire-year=2040
&finish-date=2040-01-01
&first-name=John
&interval=1
&last-name=Smith
&max-repeats-number=1000
¬ify-url=http%3A%2F%2Fexample.com%2Fnotify-me
&order_desc=testing%20purposes
&period=week
&phone=12345678
&purpose=No%20purpose%20at%20all
&rp_card_type=SRC
&ssn=1234
&start-date=2030-01-01
&state=IL
&zip-code=123456
&server_callback_url=https://httpstat.us/200
Success Response Example
HTTP/1.1 200
Server: server
Date: Thu, 18 Jul 2024 14:16:20 GMT
Content-Type: text/html;charset=utf-8
Connection: keep-alive
Keep-Alive: timeout=60
Vary: Accept-Encoding
X-XSS-Protection: 1
X-Content-Type-Options: nosniff
Strict-Transport-Security: max-age=31536000
Content-Language: en-US
Strict-Transport-Security: max-age=31536000
Content-Length: 137
type=create-recurring-payment-response
&serial-number=00000000-0000-0000-0000-000002f36d81
&recurring-payment-id=1492124
&status=approved
Fail Response Example
HTTP/1.1 500
Server: server
Date: Thu, 18 Jul 2024 14:24:28 GMT
Content-Length: 61
Connection: keep-alive
Keep-Alive: timeout=60
X-XSS-Protection: 1
X-Content-Type-Options: nosniff
Strict-Transport-Security: max-age=31536000
Internal server error [8485772c-21d6-42aa-b2eb-3b5ae4e07d19]
Postman Collection
Request Builder
Debug form
Normalized parameters string to sign, according to OAuth 1.0a rules |
---|
POST body parameters to submit |
---|
OAuth 1.0a headers to submit. |
---|
HEX Encoded Signature |
---|
Base64 Encoded Signature |
---|
|