Everyware makes HTTP requests to your application just like a regular web browser, in the format
By including parameters and values in its requests, Everyware sends data to your application that you can act upon before responding.
When Everyware receives a payment attempt for one of your contacts, it makes a synchronous HTTP
request to the message URL configured for your account.
Check Data Format
Please code to the Everyware data format so your endpoint will accept the data: application/x-www-form-urlencoded.
Everyware sends the following parameters with its request as POST parameter:
A 32 character unique identifier for the payment attempt.
This is the Everyware unique identifier for the contact.
This is the unique identifier that you provided on the initial call to create the contact.
Unique identifier for the business provided by you.
This is the email address of the contact.
This is the phone number of the contact.
This is to identify if the payment attempt was a success or failure. “0” will indicate success, and “1” will indicate failure.
This is the dollar amount of the payment attempt.
This is the date/time the payment attempt was made.
This is the transaction identifier for the successful transaction, aka InvoiceID.
Shows as the Invoice # on the customer facing invoice.
This is to identify if a full or partial payment was attempted. “P” will indicate partial, “F” will indicate full.
This is the type of card that was used for the payment attempt.
This is the last 4 digits of the card number used on the payment attempt.
This is the response message that is provided for a failed payment attempt.
To set up the Payment Webhook, log into the Everyware portal, go to Settings, open the API Settings tab, and enter the username and password under Configure Webhooks.
Updated 6 months ago