payments
Here are 709 public repositories matching this topic...
The accept button on offer pages sent to customers is pretty confusing when IN is set to German.
While not completely false, “zustimmen“ is clearly the wrong word to use here (it's rather equivalent to “agree”). The button should rather say “Angebot annehmen”. (Please note that using only the verb “Annehmen” would very likely still cause the very same confusion!)
Why does this happen?
Background
The binaries are built with most of the build flags already set, but when building from source you must specify which tags are desired. This is an important step to building a usable binary from source.
These flags should be listed in the docs, with what their use is for the entire system, and whether or not excluding it would break the normal function of the system.
A sect
When we run our invoicing logic, we print the billing events for debugging (see DefaultInternalBillingApi):
DefaultBillingEvent{type=CREATE, effectiveDate=2017-05-11T13:44:31.000Z, planPhaseName=sports-monthly-evergreen, subscriptionId=e2e74b3f-b78d-46c7-a7ff-081ff888521f, totalOrdering=1}
We should add the catalog version (catalogEffectiveDate) as well, as this would be helpfu
When I instruct the WebUI to join a token network with 5 TDAI, I get the message
TestDAI network was joined successfully with 5 TDAI
but in my case, only a single channel with a deposit of 1 TDAI has been created. The actual behavior is an expected result of our code for joining a TN. The behavior is already surprising enough, but with this message it clearly looks like a bug to the unsus
Need help to resolve this issue. @barbieri @Andreyco @miracle2k @zibs
project configuration:
`{
"name": "PaymentDemo",
"version": "0.0.1",
"private": true,
"scripts": {
"start": "react-native start",
"test": "jest",
"lint": "eslint ."
},
"dependencies": {
"react": "16.8.6",
"react-native": "0.60.4",
"react-native-payments": "^0.7.1",
"react
-
Updated
Jun 8, 2020 - JavaScript
Something based on https://docs.djangoproject.com/en/3.0/howto/upgrade-version/ would be a good idea.
- Review the change log for breaking changes
- Upgrade one feature release at a time (eg 2.2.x to 2.3.x)
- Test for deprecation warnings before/after each feature release
- Suggestion to run
./manage.py djstripe_sync_modelsafter feature release in order to populate new fields - link to h
I have been using the default version (old) of Bash in the latest macOS version and the color formatting in the usage example was not working as intended. I checked and the \e is not supported in the version that ships with macOS currently. However, I switched to zsh (5.7.1) and it was the same case there. Then upgraded Bash via homebrew (5.0.11) and I am still seeing the issue. I have been tryi
Description
I can't find any reference documentation for window.paypal anywhere?!
Obviously this link is in the README https://developer.paypal.com/docs/checkout/ however it's not really documentation. It's just a quick start + guides. Even the "reference" section isn't reference documentation (with the exception for [customizing
/service-instance/1 -> actions -> Add charge
Under the price section you can only use the arrows that show on the right to increase the price. You can't type a custom price. This field should accept keyboard input.
I'm working on a PR for #523 which necessitates updating the docs. I haven't figuring out how to preview my doc changes, particularly given I need to link between different documents. I feel like I'm missing something.
Given the docs aren't very up to date, and not well publicised, I'm considering updating the docs to use ReStructuredText/Sphinx (which I'm very familiar
-
Updated
May 29, 2020 - JavaScript
-
Updated
Jun 7, 2020 - HTML
A few things I will add once I have time, this may help the production/ live setup as PayPal is quite messy and buggy.
Quick explanation how to create access keys, for both sandbox and live;
- Have a page with more details and full guide on how to proceed;
- Add a warning for live (production) access keys that:
- Email address must be verified;
- If PayPal says you didn't veri
Randomized with seed 07249
Started
..............F...............FF..............................FFFFFFFFFFFFFFFFFFFFFF
Failures:
- payment validating card types should validate troy card types
Message:
AssertionError [ERR_ASSERTION]: troy
Stack:
error properties: Object({ generatedMessage: false, code: 'ERR_ASSERTION', actual: false, expected: true, operator: '==' })
- We would like to add ability to specify shopping cart content images in Payment Request.
- We would like to add ability to specify both the primary and the second label for shipping options. This would allow distinguishing between the shipping speed ("2-day") and the expected delivery date ("Sunday, May 5").
For example:
new PaymentRequest(paymentMethods, {
total: {label-
Updated
Feb 13, 2020 - Swift
Setup doctests
doctests will help us catch any stale examples in the documentation, in case the examples break due to changes in code.
The following need to be resolved for doctests to work:
- The outputs also have to be written down in the documentation
- Typical response objects are huge (will take up a lot of space).
- Responses are unique and can't be tested against.
- Our examples invoke calls
General information
- SDK version: v3
- Environment: https://developers.braintreepayments.com/guides/hosted-fields/overview/javascript/v3
- Browser and OS MacOS 10.15.3 Safari 13.0.5
Issue description
Issue exist on https://developers.braintreepayments.com/guides/hosted-fields/overview/javascript/v3 too. Open the link in safari, and input fields needs double tab to focus. This i
-
Updated
Jun 1, 2020 - HTML
Improve this page
Add a description, image, and links to the payments topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the payments topic, visit your repo's landing page and select "manage topics."
steps to repro: