So I'm trying to implement direct debit payments and oh boy, what a mess this has been. It's nigh impossible to find coherent docs on how this should work. There is an IbanElement component in this package but I can't find any example on how this should work, the API,...

Even simple stuff like supportedCountries=['SEPA'] I had to find out by following the error messages.

Can you guys please

\Stripe\Subscription have * @property int $trial_end but according to api documentation this can be now.

Same with * @property int $billing_cycle_anchor (it's also can be now) and * @property Plan $plan (it`s [can accept](

There may be cases when developer tries to pass private service id to payum.gateways configuration but it's ignored resulting in confusing expected object got string error.

I would like for payum to throw exception saing that service id does not exist or is private instead of acting like it was supposed to be string.

https://github.com/Payum/Payum/blob/master/src/Payum/Core/Bridge/Symfony/Co

Before I have submitted the issue

[ ] I have read an installation guide
[ ] I know that for an iOS I need to install pods because I've read the installation guide
[ ] I have read a [linking guide](https://tipsi.github.io/tipsi-stripe/docs/linking.ht

for SEO purposes, we should add some copy to the login page so google has something to munch on that isn't the meta.

AC

• SEO-driven copy written & put somewhere on the signup/login page

Estimate: 4 hours

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_models after feature release in order to populate new fields - link to h

/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.

@paltman @blueyed

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

Hi - this is a great gem, thanks for creating it and maintaining it!

First time user of Stripe, and it looks like the quick start is missing some steps right in the middle on how to initiate and complete a charge, such as for a subscription.
https://stripe.com/docs/billing/subscriptions/payment

Looks like we have:

• Creating creating products / plans
• Including the stripe elements JS

The docs specify the following attributes for creating a Stripe.Invoice

https://github.com/code-corps/stripity_stripe/blob/caa2d8dda5673e84fc5540856e9fae6b987dfe84/lib/stripe/subscriptions/invoice.ex#L182-L198

It is still possible to pass in a collection_method as specified in the Stripe API but it would be nice to have it detailed here.

It would be great if there is any documentation for all the available params to be expanded in each Stripe Object.

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:
  1. Email address must be verified;
  2. If PayPal says you didn't veri

Hello,

In the readme we don't have the location of the payum.yaml which is located at : config/packages/payum.yaml!

I think it's better to be more accurate about that :-)!

I followed the example in your docs at: https://www.npmjs.com/package/vue-stripe-elements-plus#multiple-elements but I do not see the components rendering on my screen. I threw some CSS in so you could see where the elements are supposed to be.

This is what I see:

Here is the Vue c

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:

1. 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.

2. Our examples invoke calls