Signature Verification
To confirm that the data that we are sending is authentic and comes from VoPay rather than a party pretending to be VoPay we will send you a ValidationKey. This ValidationKey is a combination of your API shared secret key and the record ID (i.e., Transaction ID, eLinx Request ID, etc) codified by HMAC SHA1
function calculateKey($apiSharedsecret, $ID)
{
return sha1($apiSharedsecret . $ID);
}
$calculateKey = calculateKey('IUAz1NGoyM02VsoODfIzQA==', '1');
if ($calculateKey == $validationKey) {
// Validation Key Ok.
} else {
// Invalid Validation Key. Ignore the webhook
}Record IDs
| Event(s) | ID | How do I find this ID? |
|---|---|---|
transactionpaymentreceived | VoPay Transaction ID | The VoPay Transaction ID is returned in the API response when submitting a transaction: { |
elinx | eLinx Request ID | The eLinx Request ID is returned in the API response when creating a eLinx request: { |
bankaccount | Bank Account Token | The Bank Account Token is returned in the API response you add a bank account via the /iq11/tokenize endpoint, or after a customer connects their bank account via the iFrame: { |
creditcard | Credit Card Token | The Credit Card Token is returned in the API response you add a credit card via the /credit-card/link-credit-card endpoint, or after a customer connects their credit card via the iFrame: { |
debitcard | Debit Card Token | The Debit Card Token is returned in the API response you add a debit card via the /debit-card/link-card endpoint, or after a customer connects their debit card via the iFrame: { |
scheduledtransactions | Scheduled Transaction ID | The Scheduled Transaction ID is returned in the API response when creating a scheduled transaction: { |
batchrequest | Batch Transaction Request ID | The Batch Transaction Request ID is returned in the API response when submitting a batch transaction request: { |
batchdetail | Batch Transaction Request Detail ID | The Batch Transaction Request Detail ID is returned in the API response when fetching the details of a batch transaction request: { "Success": "true", "ErrorMessage": "", "BatchDetails": { "0": { "ResponseData": {}, "BatchTransactionRequestDetailsRecordID": "234562", "TransactionPayload": {}, "FailureReason": "", "Status":"pending" } } |
accountonboardingaccountonboardingapplicationaccountbalanceaccountlimitrollingreserveclientaccountverificationclientaccountinformationcomplete | VoPay Account ID | The VoPay Account ID is returned in the API response when creating an account: { |
clientaccountbalance | Client Account / Contact ID | The Client Account ID is returned in the API response when creating a a client account / contact: { |
accountverifications | Verification Request ID | The Verification Request ID is returned when initiating the micro deposit transaction: { |
contactverification | Contact Verification Request ID | The Contact Verification Request ID is returned when initiating the contact verification request: { |
dataenrichment | Data Enrichment Request ID | The Data Enrichment Request ID is returned when initiating a data enrichment request: { |
transactiongroup | Transaction Group ID | The VoPay Transaction ID is returned in the API response when submitting a transaction that require a transaction group: { |
virtualtransaction | VoPay Transaction ID | The VoPay Transaction ID for a virtual transaction can be returned in the API response when fetching a transaction: { |
IP Addresses
All outbound webhook requests will originate from one of the following IP addresses:
15.156.104.253
52.60.226.121
Note that additional IP addresses may be added in the future.
Updated 8 months ago