PayNau

Introduction

API Reference

Errors

Authorization

Authentication

Oauth Token Gen

Is Alive

Payment

Transaction Config

Payment Widget

FastAPI

Paynau

Production

Sandbox

The Paynau API is organized around <a href="http://en.wikipedia.org/wiki/Representational_State_Transfer" target="_blank">REST</a>. Our API has predictable resource-oriented URLs, accepts json-encoded request bodies,returns <a href="http://www.json.org/" target="_blank">JSON-encoded</a> responses, and uses standard HTTP response codes, authentication, and verbs.You can use the Paynau API in test mode, which doesn&apos;t affect your live data or interact with the banking networks. The Paynau API doesn&apos;t support bulk updates. You can work on only one object per request.

. Our API has predictable resource-oriented URLs, accepts json-encoded request bodies,

 responses, and uses standard HTTP response codes, authentication, and verbs.

You can use the Paynau API in test mode, which doesn't affect your live data or interact with the banking networks. 

The Paynau API doesn't support bulk updates. You can work on only one object per request.

Paynau uses conventional HTTP response codes to indicate the success or failure of an API request. In general: Codes in the 2xx range indicate success. Codes in the 4xx range indicate an error that failed given the information provided (e.g., a required parameter was omitted, etc.). Codes in the 5xx range indicate an error with Paynau´s servers (these are rare).Some 4xx errors that could be handled programmatically (e.g., a card is declined) include an error code that briefly explains the error reported.

Paynau uses conventional HTTP response codes to indicate the success or failure of an API request. In general: 

Codes in the 2xx range indicate success. 

Codes in the 4xx range indicate an error that failed given the information provided (e.g., a required parameter was omitted, etc.). 

Codes in the 5xx range indicate an error with Paynau´s servers (these are rare).

Some 4xx errors that could be handled programmatically (e.g., a card is declined) include an error code that briefly explains the error reported.

200 - OK

The request was unacceptable, often due to missing a required parameter.

400 - Bad request

The request was unacceptable, often due to missing a required authorization key.

401 - Unauthorized

The parameters were valid but the request failed.

402 - Request Failed

The API key doesnt have permissions to perform the request.

403 - Forbidden

404 - Not Found

Server Errors Something went wrong on Paynau's end. (These are rare.)

500, 502, 503, 504

Bearer Token to be generated with your credentials given

detail

transaction_id

timestamp

Merchant ID, provided when completing your enrollment process

merchant_id

Total amount of the transaction, including  fees and taxes

transaction_total

payment_method_code

merchant_country

currency

paynau_date

Reference for the transaction , must be unique

merchant_transaction_reference

transaction_fields

Merchant Id provided when you complete your registration

Country where the transaction is being processed

country

value

merchantId

A unique ID used to get an authorization token in order to be able to connect to widget API's.

client_id

This is like a password to be used along with the above client_id while getting the authorization token.

client_secret

The code of the currency of the value (e.g. MXN, USD, GTQ, etc.).

currencyCode

The website owner might want to send an ID generated by him in order to track the payment transaction on his end and match later with our records.

(not required), sets a predefined style theme (e.g. "dark", "bubblegum").

theme

Configuration Object

Receive your customers' payments through this secure, embeddable UI component. 

Improve the payment experience for your users, providing different payment methods to your customers.

The installation consists on make use of a snippet of JavaScript code that can be easily inserted into any website's HTML. This doesn't require an extensive knowledge of coding.

The snippet of code to install the payment widget the looks like this:

This is a JavaScript object with the following properties:

In the code above it can be seeing that the string 

 is passed as the 4th parameter to the self-executable anonymous function (aka 

Later, the payment widget command to initialize everything is executed using the same string 

This allows us to customize the name of the commands handler in case there is a conflict with some other global key registered in the website, for example:

 and, execute custom logic after the payment has been completed, use the following code. Just make sure to use it 

If it is needed to access the payment request response after the event has been completed and without a previous subscription, it is possible to use the following code and retrieve the data: