I am using authorize.net for transaction processing.I have enable amount & transaction velocity filter in FDS(Fraud Detection Suite) for fraud prevention and also I have set action to decline the transaction when these filters are triggered. I am doing transactions to trigger these FDS filters. Filters are triggered & transactions also declined but I was not received any kind of email notification for these FDS filter triggering.
Kindly help .
Thanks
Amol
You can login to your Authorize.Net interface to configure this by going to Tools, click on Fraud Detection Suite on your left hand side, under General on your left column you will see a link for "Email Notifications". You can opt to receive an email notification each time an enabled filter is triggered by a transaction and add the email address in that page.
Related
Is there a good way to retry failed subscription payments? Sometimes our customers will fail a payment but then have money the next day, so we just want to retry the payment instead of having them update their card. Some things we've tried:
Foolishly signed up for "Automatic Retry" thinking it would automatically retry, but it only retries after the customer updates their card.
In order for Automatic Retry to kick in, the subscription needs to change from Suspended to Active which has to be done manually according to support. There's really no way to do this through the API?
Our last resort: On any failed subscription, cancel the subscription and re-create it from the profile, starting on the date we want to retry the payment. Any downsides to this I'm not considering?
There is no way to automatically retry a failed subscription payment through their API. That thread is a few years old but no new endpoints were added since then to enable this functionality.
On any failed subscription, cancel the subscription and re-create it from the profile, starting on the date we want to retry the payment. Any downsides to this I'm not considering?
You will incur transaction fees for retrying even though the chance for success is low.
Make sure you control all notifications. If your user gets emails telling them they're making unexpected payments or setting up new subscriptions you run the risk of chargebacks which could cause you to lose your ability to accept credit cards.
Prerequisites
I use AWS SES to send an email with event publishing to track the delivery status.
Problem
I'm looking for an event to make sure that an email is successfully sent to the end-user.
Description
Following AWS documentation, this type is suitable:
Deliveries – Amazon SES successfully delivered the email to the
recipient's mail server.
However, this event I get also in case Hard bounces.
For example, email status flow is:
Sends -> Deliveries - in case of successfull delivery
Sends -> Deliveries -> Hard bounces - in case I provide invalid recipient name, e.g. invalid#domain.com or 1234567890#domain.com
I don't expect Hard bounces after Deliveries.
If this behavior is correct then I need some additional event for sure success.
Something like this is expected in case of successfull delivery:
Sends -> Deliveries -> Success
I know that there are other "success" events like Opens, Clicks, Subscriptions, but they require additional action from the end-user.
Implementation details
I use Verified identity as an email sender.
A configuration set is used to redirect status events to SNS.
Finally, SQS is subscribed to this SNS to have all events in one place.
I tried several ways to send an email:
Java code using AWS SES SDK
Sending simulator with predefined and custom recipient's
The result is the same (as described above)
I think it is impossible to have a Success status because AWS cannot guarantee when the recipient mail server will reply with a Hard Bounce. You yourself have to define how long to you want to wait until you consider a delivery as successful. For example, if no hard bounce after 5 minutes, then it is a success.
If your use case is for analytics, I will simply capture more event types (for example log both Deliveries and Hard Bounces), and then count my success as Count of Deliveries - Count of Hard Bounces.
If your use case is for event-driven workloads, we need to define first what is considered a Success. For example, if we define Success as no Hard Bounce after 5 minutes, we can configure a Lambda function to trigger 5 minutes after a Delivery event. In the function, check if a subsequent Bounce event occurred. If not, the delivery is considered successful and then you can proceed to do what you want to do.
This is what I got from aws support about delivery status of an email.
Amazon SES will continue making several delivery attempts until
receiving a successful response from the recipient mail server, or
until 840 minutes elapse. If Amazon SES is still unable to deliver
the email/message during this period, it stops sending the email and
will then return a bounce message/notification.
According to this you can't be sure about the bounce or any other status within 5 minutes.
AWS does not have visibility to confirm if the Recipient Mail Server was able to deliver the message to the recipient email address when you get a 250 OK(it's confirmation that aws has delivered the message to recipient's mail server).
So there is no way you can be sure.
We ran into this issues a few times and hope to find a workaround.
screenshot of Cloud PubSub web console
As in the picture, the PubSub topic has a push subscription on it. When 'VIEW MESSAGES' was clicked, the side panel seemed to allow the user to choose a subscription. But when the user clicked on it, it was not showing the subscription. As a result, the user was not able to 'view messages'.
Is the type of subscription related to this issue or is this functionality not available? If it is related, is there a way to see messages for a topic with only a push subscription?
A push subscription don't stack the message. Each time there is a message, the push subscription sent it to the HTTP endpoint. Because of this, the subscription is always "empty".(This is not exactly true, the not acked message are in memory and are retried until the reception of HTTP code 2XX of the TTL expiration (7 days by default). But there is nothing really stored, at rest)
At the opposite, the pull subscription stack the message until the polling by a client. By the way, you can see the messages stacked.
When I debug a push subscription, especially for seeing what is the structure, the type of message and to validate this, I create a pull subscription in addition and I look into it the messages published in the topic.
I have integrated paypal-adaptive-payment-delayed-chained-payments in my Rails Application and there will Primary receiver hold whole amount and sender can cancel the product and refund the amount.
I am using paypal sandbox account for testing but getting "refund_status"=>"NO_API_ACCESS_TO_RECEIVER" this after call refund and paypal success is true
so I am confusing what that mean, as I know in sandbox paypal provide full access
log is:
{"response_envelope"=>{"timestamp"=>"2015-10-06T22:55:49.604-07:00", "ack"=>"Success", "correlation_id"=>"9f0f563554297", "build"=>"17820627"}, "currency_code"=>"USD", "refund_info_list"=>{"refund_info"=>[{"receiver"=>{"amount"=>"60.00", "email"=>"test#gmail.com"}, "refund_status"=>"NO_API_ACCESS_TO_RECEIVER"}]}}
Please let me know where I am doing wrong
The status NO_API_ACCESS_TO_RECEIVER indicates that the request cannot be completed because you do not have third-party access from the receiver to make the refund.
Sandbox account has provided full access but when it comes to Adaptive Payments (Chained) Refund in particular, you would need your refund API caller (in your case, the primary receiver) to be granted with refund permission (3rd party access to make a refund on-behalf) from all secondary recievers in the chain.
Check HERE (the Refund API Overview section) for instructions
We want to push legency system's log to BAM, and to send email to administrator if an exception occurs.
Data publisher helps a lot, but I don't know about CEP. How can I manage the email sent real time?
If you are analyzing the logs real-time, you can use WSO2 CEP with an email output event adaptor to generate notifications as emails. For a sample on generating email notifications, you can refer to sample no. 0106 here.
You will have to write a query to detect exceptions in the logs here. Writing a filter query with 'contains' clause may be enough if you are just detecting the occurrences of word 'exception'. You can find documentation on writing filters here.