I trying to determine wallet address to which the payment was received.
In the transaction resource description I see the address field, that should to be exactly what i'm looking for. But API don't returns this field with transaction object.
Related
When using Azure Logic App Office 365 Outlook connector - "Send an email", is there a way to find out if the email was actually delivered or not to the recipient so as to take a specific action based on the failure?
I used an invalid email ID in the connector, but the action of sending email is shown as successful even though the email was not delivered. To confirm it is an invalid email ID, I sent email to this invalid email ID from my Outlook and I received an undelivered email message.
In the next action after this “Send an email” action, I selected the 3 options (has failed, is skipped, has timed out) under “Configure run after”. However, this action is never executed as the email sending action is always successful even though the email was never delivered to the user.
Below is a screenshot of my logic app. The bottom right action in yellow is never executed even though the email is not sent in the previous step.
Send Email Logic App
Any inputs on how I can find out if the email was actually delivered or not?
My goal here is to find out if the user actually received the email or not, and then take some action if the email delivery failed.
No, this is not possible from within the Logic App.
The only way to occasionally accomplish this is to monitor the sender inbox for NDRs (Non-Delivery Receipt). This can take minutes to hours.
Be aware, a number of email systems will not even send NDRs as they can be used to fish for email addresses.
You can use get emails action to get the latest email and you can perform the next action based on the condition whether the subject of the email we get contains the "Undelivered" string.
Sometimes it takes long to receive the undelivered report email in outlook. so i made a specific flow which will extract the wrong email that i sent the mail to and send me an adaptive card with that email provided in it.
Is it possible to set a fee (miner fee) on a transaction when sending BTC / ETH / LTC using the Coinbase Wallet API?
What I know:
Coinbase automatically sets the fee when using the website and this can't be customised.
The API documentation shows a parameter where one should be able to specify the fee (https://developers.coinbase.com/api/v2#send-money). However, making any requests with this parameter returns an error message:
{"errors":[{"id":"validation_error","message":"The transaction fee has expired."}]}
Just want to know if it is possible to specify a fee at all, and if so how you went about it.
The scenario is that users of web application can purchase digital items. The web application will use Paypal Instant Payment Notification.
The IPN protocol consists of three steps:
PayPal sends your IPN listener a message that notifies you of the event
Your listener sends the complete unaltered message back to PayPal; the message must contain the same fields in the same order and be encoded in the same way as the original message
PayPal sends a single word back, which is either VERIFIED if the message originated with PayPal or INVALID if there is any discrepancy with what was originally sent.
Let's say it's VERIFIED, how could I know who have completed the transaction or purchased the item (user of the web application) if the user used other email address in his/her paypal? I have stored the email address of the user in session but what if he/she have different paypal email? Paypal email is included in IPN message.
For other details, maybe not useful, the application is written in Struts2 in Google-App-Engine.
You'll need a way to correlate the IPN data coming back with the user. Either by asking them to provide their paypal email or using the username/password generation facility in the IPN service. Here is a somewhat inelegant but functional approach:
When the IPN comes in off the wire, persist the paypal generated username/password and payer_id (in perhaps the datastore).
If you can't correlate by email, then when the user comes back to your site request that they enter the username/password generated from paypal's site once (just to correlate).
Lookup the username/password and then correlate their userid from the UserService back to the payerid.
The reason to use IPN is for subscription services as you can get IPN messages when the subscription is terminated, cancelled, or when payments come in (for an account that stopped paying).
The most important thing to think about is how to correlate a user of your site back to the payer_id (or even payer_ids in some cases) that are used to pay for the services they are using.
On another note, I wouldn't use the session to store information for IPN callbacks, those actually can take a LONG time sometimes (say when the x.com conference is on and everyone is hammering paypal).
If you have a running application or a better description of the look & feel, I might be able to come up with a more elegant suggestion. Let me know if this helps at all.
Why don't you use PayPal's express checkout? This way you negotiate server2server a token and then you can check with PayPal the result of that token on user's return.
If users are buying directly from your application it's easier to implement.
And I think it'is more robust than the method you're using (I never heard of it before :D )
I'm trying to advance my programming skills and as such I'm trying to create a website which integrates with paypal. I've established that I need to be using chained payments through the adaptive payments API.
But before I go about receiving and sending payments I want to make sure that any new user signing up to my website already has a paypal account. IE when they sign up to my website I'd like to first of all check that the email address they supplied me with is already linked to a valid paypal account.
I've never had to do this before so if someone could explain in very simple language how I might go about doing this I'd be really grateful.
I'm using the cakephp framework incase that makes any difference to the answer.
thanks
This may be what you're looking for: AddressVerify API
Confirms whether a postal address and postal code match those of the
specified PayPal account holder.
After supplying an email address, PayPal will return with one of 3 responses for the email parameter: None, Confirmed, or Unconfirmed. If it is None, then the request value does not match any email address on file at PayPal.
Although this API requires both the email address and shipping/billing information, it can be solely used to verify the email address. By supplying invalid shipping/billing information, the API will still respond with whether the email matches any on file at PayPal, and also match whether your invalid shipping/billing information matches the information on file with the matched email address.
An expected PayPal response may reflect the above:
Array
(
[CONFIRMATIONCODE] => Confirmed
[STREETMATCH] => Unconfirmed
[ZIPMATCH] => Unconfirmed
[COUNTRYCODE] => US
[TOKEN] => a134k1j34lk134gv13dshjg52b
)
CONFIRMATIONCODE will be your only concern when verifying a PayPal email address.
Please, check the above link for more information.
Setting up an IPN Listener is one way that's often used to verify most of the important information you're referring to. There's a decent tutorial that you can check out since paypal's example might not be enough on it's own.
My mail is regarding the option for receiving email to any address which looks like - xxx#appid.appspotmail.com documented here: http://code.google.com/appengine/docs/python/mail/receivingmail.html
My questions are:
Is there any restriction on the number of email addresses which can be created using the above format and used inside the application?
As an example I may have a million users and could have some sort of a "in-mail" facility where each user is assigned a unique "xxx" id.
Is there any limit on the number of emails which can be received by an address of the above format? I don't see any quota restrictions specified anywhere?
There's no limit to the number of email addresses you can send or receive email on. Incoming email is simply sent to your handler with the address preserved; no accounts get created, so there's no reason to limit the number of unique addresses. The system-wide quota limits on incoming mail, total requests, and calls to the mail API are the only ones that apply here.
There is no limit on the number of addresses where your app can receive mail, or the number of emails it can receive.
App Engine does not persist the addresses you've used to receive mail; each inbound message is handled like an HTTP POST and then discarded. Sending a million emails to one address or a to million addresses will use the same resources.
The mail-related quotas apply to sent mail only. For CPU, bandwidth, etc., inbound mail draws from the same resource pool as your HTTP requests. There's no indication in the docs of any quota specific to inbound mail.
I can't see any mention of a maximum of email addresses you can have in the format
string# appid.appspotmail.com. But surely there must be some internal limit specified. I guess the appspotmail option is not meant to be used to create unique emails for each of your app's users (especially if you have a large number of users).
There are limits specified in the quotas, for example you can send mails to a maximum of 7,400,000 recipients a day, and you can make a maximum of 1,700,000 calls a day to the GAE Mail API (both limits apply only when billing is enabled). So if you had a million users, you probably would reach the API limit pretty soon when most of them would receive one or multiple emails.